mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: mario.limonciello@amd.com, tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: [PATCH v3] x86/CPU/AMD: Prefix messages with x86/amd
Date: Sat, 10 Jan 2026 16:44:37 -0600	[thread overview]
Message-ID: <ad197d3e-f220-40d3-a775-84d9f6a8c4f8@kernel.org> (raw)
In-Reply-To: <20260110135349.GBaWJZ7RayAKdIamdY@fat_crate.local>



On 1/10/2026 7:53 AM, Borislav Petkov wrote:
> On Sat, Jan 10, 2026 at 07:39:35AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
>> Well originally the reason was that another message was being added in a
>> series.  But the review of the series was deciding not to do it that way.
>> But this way any other future messages pick up the prefix already.
>>
>> It's a trivial patch, but if you want to wait until another message comes
>> around again we can hold off.
> 
> I'm actually wondering whether there's any specific reason to denote that the
> messages come from this particular compilation unit...?
> 

My own personal use when looking at very noisy logs is to use "grep -v" 
and filter out prefixes.  Don't know if other people do that.

      reply	other threads:[~2026-01-10 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 19:33 Mario Limonciello (AMD)
2026-01-09 19:45 ` Borislav Petkov
2026-01-10 13:39   ` Mario Limonciello (AMD) (kernel.org)
2026-01-10 13:53     ` Borislav Petkov
2026-01-10 22:44       ` Mario Limonciello (AMD) (kernel.org) [this message]

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=ad197d3e-f220-40d3-a775-84d9f6a8c4f8@kernel.org \
    --to=superm1@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@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

all inboxes | Powered by JetHome®