mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Mike Snitzer <snitzer@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jens Axboe <axboe@kernel.dk>,  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 20:51:17 +0200 (CEST)	[thread overview]
Message-ID: <ebfd8bf4-6260-f04-38f9-2ec234968171@redhat.com> (raw)
In-Reply-To: <Zo_mnW5NcRBkWejT@kernel.org>



On Thu, 11 Jul 2024, Mike Snitzer wrote:

> > 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.

I probably badly understood it, I added the patch to my notes and then I 
thought that I should apply it. Sorry for that.

Mikulas

> 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
> 


  reply	other threads:[~2024-07-11 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- 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=ebfd8bf4-6260-f04-38f9-2ec234968171@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=snitzer@kernel.org \
    /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

all inboxes | Powered by JetHome®