linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	akpm@linux-foundation.org, Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v6 0/4] Convert x86/mm/pat to generic page table apis
Date: Mon, 2 Mar 2026 14:43:37 -0800	[thread overview]
Message-ID: <aaYSmajuukDL869D@fedora> (raw)
In-Reply-To: <c85f864e-7784-4ba4-9fae-e957b6305d92@intel.com>

On Mon, Mar 02, 2026 at 12:55:10PM -0800, Dave Hansen wrote:
> On 3/2/26 12:27, Vishal Moola (Oracle) wrote:
> >> I was actually kinda hoping you'd be able to actively go out and find
> >> some reviewers other than the maintainers.
> > I'd appreciate if you could give me more guidance on this. Who am I
> > supposed to go, if not the people from ./get_maintainers? I don't know
> > the x86 folks, I interact more with mm.
> 
> Hi Vishal,
> 
> I personally look at 'git blame' or 'git log' manually and see who's
> been mucking around in the file recently. get_maintainers.pl does _some_
> of that, but I think it mostly looks at others who modified the sames
> lines you did. That can be a bit too restrictive.
> 
> It also couldn't hurt to take a quick look at lore for who's been
> patching the files that you are, or commenting in threads.
> 
> The more of that which you can manage to do this now is less of it that
> I have to do later. Any effort in the area would be much appreciated!

Thanks! I'll look around and cc them on future versions.

> Oh, and if you have a friendly LLM, it doesn't hurt to dump your patches
> in there and ask it. Couldn't hurt.


      reply	other threads:[~2026-03-02 22:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  2:03 Vishal Moola (Oracle)
2026-02-19  2:03 ` [PATCH v6 1/4] x86/mm/pat: Convert pte code to use " Vishal Moola (Oracle)
2026-02-19  2:03 ` [PATCH v6 2/4] x86/mm/pat: Convert pmd " Vishal Moola (Oracle)
2026-02-19  2:03 ` [PATCH v6 3/4] x86/mm/pat: Convert populate_pgd() " Vishal Moola (Oracle)
2026-02-19  2:03 ` [PATCH v6 4/4] x86/mm/pat: Convert split_large_page() to use ptdescs Vishal Moola (Oracle)
2026-02-20 10:25 ` [PATCH v6 0/4] Convert x86/mm/pat to generic page table apis Mike Rapoport
2026-02-27 20:07 ` Vishal Moola (Oracle)
2026-02-27 22:24   ` Dave Hansen
2026-02-28  0:44     ` Vishal Moola (Oracle)
2026-03-02 17:33       ` Dave Hansen
2026-03-02 20:27         ` Vishal Moola (Oracle)
2026-03-02 20:55           ` Dave Hansen
2026-03-02 22:43             ` Vishal Moola (Oracle) [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=aaYSmajuukDL869D@fedora \
    --to=vishal.moola@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rppt@kernel.org \
    --cc=tglx@kernel.org \
    --cc=willy@infradead.org \
    --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