Linux real-time development
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: "shaikh.kamal" <shaikhkamal2012@gmail.com>
Cc: "Liam R. Howlett" <liam@infradead.org>,
	 Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	 Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	 David Rientjes <rientjes@google.com>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	 pbonzini@redhat.com, skhan@linuxfoundation.org,
	me@brighamcampbell.com,
	 syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 1/1] mm/mmu_notifier: Add async OOM cleanup via call_srcu()
Date: Mon, 8 Jun 2026 09:30:51 +0100	[thread overview]
Message-ID: <aiZ4-4VVJTjIJB24@lucifer> (raw)
In-Reply-To: <20260429222548.25475-1-shaikhkamal2012@gmail.com>

-cc my + Liam's incorrect email addresses, +cc Liam's correct one.

Hi Shaikh,

I'm assuming you're fairly new to the kernel so some feedback here, as
there's quite a bit wrong with these patches.

Firstly, please check MAINTAINERS to ensure you have the right email addresses.

Also please don't send mm patches in-reply-to another series, send them as
separate series.

Send patch series such that they're in-reply-to the cover letter. Do not
send a cover letter if there's only one patch in the series.

Do not send follow up series in-reply-to the previous version. Send a new
patch or patch series.

If you get an issue like a build failure, do not reply-to the patch that
failed with a fix, instead send a new version of that patch with the fix.

When you fix things, add a brief changelog under the '---' line if a single
patch, or at the bottom before the diffstat if a cover letter. Ideally with
lore links to previous versions.

For patch series use:

$ git format-patch --cover-letter --thread FIRST_PATCH_HASH~1

For v2, v3 etc. use:

$ git format-patch -v2 --cover-letter --thread FIRST_PATCH_HASH~1
$ git format-patch -v3 --cover-letter --thread FIRST_PATCH_HASH~1
etc.

More useful tips here:

https://docs.kernel.org/process/submitting-patches.html

An example of a series with these traits:

https://lore.kernel.org/all/cover.1774029655.git.ljs@kernel.org/

Thanks, Lorenzo

  parent reply	other threads:[~2026-06-08  8:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 13:15 [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT shaikh.kamal
2026-03-30 14:18 ` Steven Rostedt
2026-03-30 14:51   ` Woodhouse, David
2026-04-01 15:40     ` Sean Christopherson
2026-04-02  1:31       ` [PATCH v2 1/1] KVM: x86/xen: Use trylock for fast path event channel delivery shaikh.kamal
2026-04-02  6:36         ` Sebastian Andrzej Siewior
2026-04-02 22:40           ` Sean Christopherson
2026-04-02  6:42       ` [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT Sebastian Andrzej Siewior
2026-04-02 22:23         ` Sean Christopherson
2026-04-29 22:25       ` [PATCH v2 1/1] mm/mmu_notifier: Add async OOM cleanup via call_srcu() shaikh.kamal
2026-05-03  3:26         ` kernel test robot
2026-05-03  3:26         ` kernel test robot
2026-06-08  8:30         ` Lorenzo Stoakes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-30 11:24 [PATCH] KVM: mmu_notifier: make mn_invalidate_lock non-sleeping for non-blocking invalidations Paolo Bonzini
2026-04-30 14:17 ` [PATCH v2 1/1] mm/mmu_notifier: Add async OOM cleanup via call_srcu() shaikh.kamal
2026-04-30  4:48 shaikh.kamal

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=aiZ4-4VVJTjIJB24@lucifer \
    --to=ljs@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=me@brighamcampbell.com \
    --cc=mhocko@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=rientjes@google.com \
    --cc=rppt@kernel.org \
    --cc=shaikhkamal2012@gmail.com \
    --cc=shakeel.butt@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com \
    --cc=vbabka@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