From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sairaj Kodilkar <sarunkod@amd.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alejandro Jimenez" <alejandro.j.jimenez@oracle.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com,
richard.henderson@linaro.org, suravee.suthikulpanit@amd.com,
vasant.hegde@amd.com, marcel.apfelbaum@gmail.com,
eduardo@habkost.net, santosh.shukla@amd.com, aik@amd.com
Subject: Re: [PATCH 0/2] Cleanups and fixes (PART 2)
Date: Fri, 10 Oct 2025 02:39:56 -0400 [thread overview]
Message-ID: <20251010023917-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <29d20903-e255-4398-90f3-5e04391a46fb@amd.com>
On Fri, Oct 10, 2025 at 10:55:45AM +0530, Sairaj Kodilkar wrote:
>
>
> On 10/10/2025 7:49 AM, Philippe Mathieu-Daudé wrote:
> > Hi Alejandro,
> >
> > On 10/10/25 03:33, Alejandro Jimenez wrote:
> >
> > > I know the commit log is not consistent so far, but going forward I
> > > propose we adopt the shorter prefix "amd_iommu: " for commit
> > > summaries. There is no ambiguity (only one arch has amd_iommu), so
> > > the full path is not required (i.e. avoid 'hw/i386/amd_iommu: ').
> > > Shorter boilerplate leaves more space for relevant details, and
> > > helps people like me who struggle to comply with character limits
> > > :).
> >
> > What about "hw/amd_iommu:" to keep 'hw' in subject?
> I also prefer "amd_iommu". But I'll wait for alejandro's reply before
> posting V2.
If possible, pls use that prefix on the cover letter too.
Thanks!
--
MST
next prev parent reply other threads:[~2025-10-10 6:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 16:43 [PATCH 0/2] Cleanups and fixes (PART 2) Sairaj Kodilkar
2025-10-08 16:43 ` [PATCH 1/2] hw/i386/amd_iommu: Fix handling device on buses != 0 Sairaj Kodilkar
2025-10-09 16:17 ` Alejandro Jimenez
2025-10-10 5:04 ` Sairaj Kodilkar
2025-10-08 16:43 ` [PATCH 2/2] hw/i386/amd_iommu: Support 64 bit address for IOTLB lookup Sairaj Kodilkar
2025-10-10 1:22 ` Alejandro Jimenez
2025-10-10 5:14 ` Sairaj Kodilkar
2025-10-10 1:33 ` [PATCH 0/2] Cleanups and fixes (PART 2) Alejandro Jimenez
2025-10-10 2:19 ` Philippe Mathieu-Daudé
2025-10-10 5:25 ` Sairaj Kodilkar
2025-10-10 6:39 ` Michael S. Tsirkin [this message]
2025-10-10 14:37 ` Alejandro Jimenez
2025-10-10 14:45 ` Michael S. Tsirkin
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=20251010023917-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aik@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=santosh.shukla@amd.com \
--cc=sarunkod@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.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;
as well as URLs for NNTP newsgroup(s).