From: Reinette Chatre <reinette.chatre@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>, <tony.luck@intel.com>,
<Dave.Martin@arm.com>, <james.morse@arm.com>,
<babu.moger@amd.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>
Cc: <sean@ashe.io>, <neelx@suse.com>, <mproche@gmail.com>,
<chjohnst@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [v4 PATCH 1/1] x86/resctrl: Add "*" shorthand to set io_alloc CBM for all domains
Date: Mon, 2 Feb 2026 20:28:11 -0800 [thread overview]
Message-ID: <a963b6f9-ef96-4fb8-949f-c7d63f70aaa8@intel.com> (raw)
In-Reply-To: <b3c1e304-85e8-421f-9a31-bcf1443c2545@intel.com>
Hi Aaron,
On 2/2/26 8:26 PM, Reinette Chatre wrote:
> Hi Aaron,
>
> No need to add a cover letter when there is just one patch. From what
> I can tell the cover letter contains duplicate text so can just be
> dropped in the next version. Although, there may possibly be two patches
> in next version (more later).
>
> For the subject, please follow the custom to have the "PATCH" text
> be the prefix. Specifically "[PATCH vX]". For reference, see
> "Subject Line" in Documentation/process/submitting-patches.rst.
One addendum here, please update the subject prefix to "fs/resctrl:" to
match the area of code modified.
Reinette
next prev parent reply other threads:[~2026-02-03 4:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 17:17 [v4 PATCH 0/1] " Aaron Tomlin
2026-01-25 17:17 ` [v4 PATCH 1/1] " Aaron Tomlin
2026-02-02 20:18 ` Babu Moger
2026-02-03 4:26 ` Reinette Chatre
2026-02-03 4:28 ` Reinette Chatre [this message]
2026-02-07 23:28 ` Aaron Tomlin
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=a963b6f9-ef96-4fb8-949f-c7d63f70aaa8@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=atomlin@atomlin.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=chjohnst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=sean@ashe.io \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®