public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel•dk>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Alasdair G Kergon <agk@redhat•com>,
	Mike Snitzer <snitzer@kernel•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 patch in the device-mapper tree
Date: Thu, 11 Jul 2024 00:16:20 -0600	[thread overview]
Message-ID: <947e6d6b-f798-4f04-b6d7-d18ad550db66@kernel.dk> (raw)
In-Reply-To: <20240711121729.0d71308e@canb.auug.org.au>

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



  reply	other threads:[~2024-07-11  6:16 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 [this message]
2024-07-11 14:05   ` Mike Snitzer
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=947e6d6b-f798-4f04-b6d7-d18ad550db66@kernel.dk \
    --to=axboe@kernel$(echo .)dk \
    --cc=agk@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=snitzer@kernel$(echo .)org \
    /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