From: Mike Snitzer <snitzer@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the device-mapper tree
Date: Wed, 13 Mar 2024 18:30:06 -0400 [thread overview]
Message-ID: <ZfIo7nbWA3pSeY3z@redhat.com> (raw)
In-Reply-To: <20240314084050.2fe3eb9f@canb.auug.org.au>
On Wed, Mar 13 2024 at 5:40P -0400,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 2da6b3c1317e ("Revert "dm: use queue_limits_set"")
>
> This is commit
>
> bff4b74625fe ("Revert "dm: use queue_limits_set"")
>
> in Linus' tree.
Sorry about that, fixed it up.
next prev parent reply other threads:[~2024-03-13 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:40 linux-next: duplicate patch in the device-mapper tree Stephen Rothwell
2024-03-13 22:30 ` Mike Snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-11 2:17 Stephen Rothwell
2024-07-11 6:16 ` Jens Axboe
2024-07-11 14:05 ` Mike Snitzer
2024-07-11 18:51 ` Mikulas Patocka
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=ZfIo7nbWA3pSeY3z@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--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.