From: Mike Snitzer <snitzer@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Jens Axboe <axboe@kernel.dk>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
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: Thu, 11 Jul 2024 10:05:17 -0400 [thread overview]
Message-ID: <Zo_mnW5NcRBkWejT@kernel.org> (raw)
In-Reply-To: <947e6d6b-f798-4f04-b6d7-d18ad550db66@kernel.dk>
On Thu, Jul 11, 2024 at 12:16:20AM -0600, Jens Axboe wrote:
> On 7/10/24 8:17 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the block tree as a different commit
> > (but the same patch):
> >
> > e87621ac68fe ("dm: Refactor is_abnormal_io()")
> >
> > This is commit
> >
> > ae7e965b36e3 ("dm: Refactor is_abnormal_io()")
> >
> > in the block tree.
Hi Stephen,
I've fixed this. But FYI, you didn't send mail to Mikulas who was the
committer in this instance.
> Looks like the dm tree is re-applying patches yesterday rather
> than pulling in the dependency?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-6.11&id=e87621ac68fec9086d9f0af4fe96594dd8e07fbb
>
> why?
Really good question.
Mikulas has been handling DM for the 6.11 development cycle. But I've
helped answer question and such along the way. We actually had a
meeting on Tuesday to discuss outstanding patches (in patchwork) and
specifically discussed this very patch. At the time I said I would
get with you to make sure you were the one to pick up Damien's 5
patches (which included what is now commit e87621ac68fe in block). I
specifically said that the entire series should go through block
because even if DM picked up the one "dm: Refactor is_abnormal_io()"
it'd cause problems because block would then depend on DM for a simple
prep commit needed for later a patch in series.
Anyway, I later saw you had already picked up Damien's series and had
no need to reach out to you, I noted as much to a group chat at Red
Hat (Mikulas included). So not really sure what happened.
Sorry for the noise/trouble.
Mike
next prev parent reply other threads:[~2024-07-11 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 2:17 linux-next: duplicate patch in the device-mapper tree Stephen Rothwell
2024-07-11 6:16 ` Jens Axboe
2024-07-11 14:05 ` Mike Snitzer [this message]
2024-07-11 18:51 ` Mikulas Patocka
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 21:40 Stephen Rothwell
2024-03-13 22:30 ` Mike Snitzer
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=Zo_mnW5NcRBkWejT@kernel.org \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).