From: Vlastimil Babka <vbabka@suse•cz>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Andrew Morton <akpm@linux-foundation•org>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: 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 mm tree
Date: Fri, 13 Jan 2023 12:11:54 +0100 [thread overview]
Message-ID: <eb806f57-15bf-eb7c-97ff-8c4f5dfd2c84@suse.cz> (raw)
In-Reply-To: <20230113142306.27e2ee60@canb.auug.org.au>
On 1/13/23 04:23, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in other -next trees tree as different
> commits (but the same patches):
>
> 280691a45437 ("mm/slab: add is_kmalloc_cache() helper function")
> (commit 61df28eb7788f in the slab tree)
Oops, that was unintentional on the slab tree side. It's part of 2-patch
series where the second one also depends on other changes in mm tree, so
both are going through mm. Will drop, thanks.
> a8197833a9d3 ("kernel/irq/manage.c: disable_irq() might sleep.")
> (commit 17549b0f184d ("genirq: Add might_sleep() to disable_irq()")
> in the tip tree)
>
next prev parent reply other threads:[~2023-01-13 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 3:23 linux-next: duplicate patches in the mm tree Stephen Rothwell
2023-01-13 11:11 ` Vlastimil Babka [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-17 23:47 Stephen Rothwell
2023-09-04 22:38 Stephen Rothwell
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=eb806f57-15bf-eb7c-97ff-8c4f5dfd2c84@suse.cz \
--to=vbabka@suse$(echo .)cz \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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