Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] MAINTAINERS: Add selftests/x86 entry
Date: Wed, 31 Jul 2024 23:23:25 +0200	[thread overview]
Message-ID: <20240731212325.GY40213@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <257c9106-c33a-46c1-9761-111505309176@linuxfoundation.org>

On Wed, Jul 31, 2024 at 12:14:16PM -0600, Shuah Khan wrote:
> On 7/31/24 07:42, Muhammad Usama Anjum wrote:
> > Kind reminder
> > 
> > On 7/2/24 3:17 PM, Muhammad Usama Anjum wrote:
> > > Kind reminder
> 
> Top post ???
> 
> > > 
> > > On 6/10/24 10:28 AM, Muhammad Usama Anjum wrote:
> > > > There are no maintainers specified for tools/testing/selftests/x86.
> > > > Shuah has mentioned [1] that the patches should go through x86 tree or
> > > > in special cases directly to Shuah's tree after getting ack-ed from x86
> > > > maintainers. Different people have been confused when sending patches as
> > > > correct maintainers aren't found by get_maintainer.pl script. Fix
> > > > this by adding entry to MAINTAINERS file.
> > > > 
> > > > [1] https://lore.kernel.org/all/90dc0dfc-4c67-4ea1-b705-0585d6e2ec47@linuxfoundation.org
> > > > 
> > > > Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> > > > ---
> > > >   MAINTAINERS | 1 +
> > > >   1 file changed, 1 insertion(+)
> > > > 
> 
> Applied to linux-kselftest next for Linux 6.12-rc1.

You are applying things for the x86 entry, without an x86 ack, srsly?

  reply	other threads:[~2024-07-31 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  5:28 [PATCH] MAINTAINERS: Add selftests/x86 entry Muhammad Usama Anjum
2024-07-02 10:17 ` Muhammad Usama Anjum
2024-07-31 13:42   ` Muhammad Usama Anjum
2024-07-31 18:14     ` Shuah Khan
2024-07-31 21:23       ` Peter Zijlstra [this message]
2024-08-01 19:27         ` Shuah Khan
2024-08-01 19:57           ` Shuah Khan
2024-08-28 17:18 ` Dave Hansen

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=20240731212325.GY40213@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@linutronix.de \
    --cc=usama.anjum@collabora.com \
    --cc=x86@kernel.org \
    /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