From: "Michael S. Tsirkin" <mst@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the vhost tree
Date: Thu, 9 Jan 2025 02:45:41 -0500 [thread overview]
Message-ID: <20250109024408-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250108212355.6e6fad4a57d23eeedecc6852@linux-foundation.org>
On Wed, Jan 08, 2025 at 09:23:55PM -0800, Andrew Morton wrote:
> On Thu, 9 Jan 2025 14:40:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > The following commits are also in the mm tree as different commits
> > (but the same patches):
> >
> > e981e8d8b23e ("s390/kdump: virtio-mem kdump support (CONFIG_PROC_VMCORE_DEVICE_RAM)")
> > a4bba3b65c20 ("virtio-mem: support CONFIG_PROC_VMCORE_DEVICE_RAM")
> > b9ad8a711a3c ("virtio-mem: remember usable region size")
> > a8328b40b3b0 ("virtio-mem: mark device ready before registering callbacks in kdump mode")
> > ef78030ec96f ("fs/proc/vmcore: introduce PROC_VMCORE_DEVICE_RAM to detect device RAM ranges in 2nd kernel")
> > a127bc45d3de ("fs/proc/vmcore: factor out freeing a list of vmcore ranges")
> > 98c5f8c3827a ("fs/proc/vmcore: factor out allocating a vmcore range and adding it to a list")
> > 5488433f810c ("fs/proc/vmcore: move vmcore definitions out of kcore.h")
> > 23365031b34f ("fs/proc/vmcore: prefix all pr_* with "vmcore:"")
> > 006f0492f363 ("fs/proc/vmcore: disallow vmcore modifications while the vmcore is open")
> > 26b866c242e5 ("fs/proc/vmcore: replace vmcoredd_mutex by vmcore_mutex")
> > 5c04c6205add ("fs/proc/vmcore: convert vmcore_cb_lock into vmcore_mutex")
> >
> > These are commits
> >
> > 9e85e500e8b3 ("s390/kdump: virtio-mem kdump support (CONFIG_PROC_VMCORE_DEVICE_RAM)")
> > 5605b723bbc2 ("virtio-mem: support CONFIG_PROC_VMCORE_DEVICE_RAM")
> > 3a365d7b1a60 ("virtio-mem: remember usable region size")
> > e4c56e7d625f ("virtio-mem: mark device ready before registering callbacks in kdump mode")
> > 342dc629fe62 ("fs/proc/vmcore: introduce PROC_VMCORE_DEVICE_RAM to detect device RAM ranges in 2nd kernel")
> > 44df29fb6c95 ("fs/proc/vmcore: factor out freeing a list of vmcore ranges")
> > 10a41d9df694 ("fs/proc/vmcore: factor out allocating a vmcore range and adding it to a list")
> > e8685745122c ("fs/proc/vmcore: move vmcore definitions out of kcore.h")
> > cfc7a194e459 ("fs/proc/vmcore: prefix all pr_* with "vmcore:"")
> > 19b42b73afa4 ("fs/proc/vmcore: disallow vmcore modifications while the vmcore is open")
> > 527d8662c520 ("fs/proc/vmcore: replace vmcoredd_mutex by vmcore_mutex")
> > 9a775759ac92 ("fs/proc/vmcore: convert vmcore_cb_lock into vmcore_mutex")
> >
> > in the mm-unstable branch of the mm tree.
>
> Thanks, I dropped the mm.git copy.
I looked at a wrong tree and thought these were forgotten,
so I put them in mine.
Andrew, good thing I saw your mail before dropping mine ;)
Can I get your ack on the mm things pls?
--
MST
next prev parent reply other threads:[~2025-01-09 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 3:40 linux-next: duplicate patches in the vhost tree Stephen Rothwell
2025-01-09 5:23 ` Andrew Morton
2025-01-09 7:45 ` Michael S. Tsirkin [this message]
2025-01-10 0:48 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2025-11-16 19:54 Stephen Rothwell
2025-10-19 20:54 Stephen Rothwell
2025-05-29 22:17 Stephen Rothwell
2024-04-23 5:33 Stephen Rothwell
2023-02-03 2:26 Stephen Rothwell
2023-02-03 2:33 ` Stephen Rothwell
2023-02-03 9:34 ` 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=20250109024408-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.