From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] pvestatd: fix container cpuset scheduling
Date: Thu, 3 Dec 2020 16:38:28 +0100 [thread overview]
Message-ID: <76c2a8a3-4187-c3be-e9af-ad77f158817a@proxmox.com> (raw)
In-Reply-To: <5b89c12c-ce1b-cf57-337c-4ca7b333c2cd@proxmox.com>
On 03.12.20 16:35, Aaron Lauterer wrote:
> Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>
saw this to late for adding it into the commit message, still thanks for
the feedback though!
next prev parent reply other threads:[~2020-12-03 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 15:01 Dominik Csapak
2020-12-03 15:35 ` Aaron Lauterer
2020-12-03 15:38 ` Thomas Lamprecht [this message]
2020-12-03 15:37 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76c2a8a3-4187-c3be-e9af-ad77f158817a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox