[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <947e6d6b-f798-4f04-b6d7-d18ad550db66@kernel.dk>
Date: Thu, 11 Jul 2024 00:16:20 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Alasdair G Kergon <agk@...hat.com>, Mike Snitzer <snitzer@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the device-mapper tree
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.
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?
--
Jens Axboe
Powered by blists - more mailing lists