From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] fix and cleanup device mapper bioset initialization
Date: Thu, 9 Jun 2022 06:11:49 +0200 [thread overview]
Message-ID: <20220609041149.GA31649@lst.de> (raw)
In-Reply-To: <YqDneqyp33PvkCLm@redhat.com>
On Wed, Jun 08, 2022 at 02:16:26PM -0400, Mike Snitzer wrote:
> All looks good to me. Are you OK with me picking up the first 3 to
> send to Linus for 5.19-rc2 (given the integrity bioset fix)?
>
> And hold patch 4 until 5.20 merge?
Sounds good to me.
> Or would you prefer that cleanup to land now too?
I don't think Linus would like that :) In fact even patch 3 might be
5.20 material.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
dm-devel@redhat.com, linux-block@vger.kernel.org
Subject: Re: fix and cleanup device mapper bioset initialization
Date: Thu, 9 Jun 2022 06:11:49 +0200 [thread overview]
Message-ID: <20220609041149.GA31649@lst.de> (raw)
In-Reply-To: <YqDneqyp33PvkCLm@redhat.com>
On Wed, Jun 08, 2022 at 02:16:26PM -0400, Mike Snitzer wrote:
> All looks good to me. Are you OK with me picking up the first 3 to
> send to Linus for 5.19-rc2 (given the integrity bioset fix)?
>
> And hold patch 4 until 5.20 merge?
Sounds good to me.
> Or would you prefer that cleanup to land now too?
I don't think Linus would like that :) In fact even patch 3 might be
5.20 material.
next prev parent reply other threads:[~2022-06-09 4:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:34 [dm-devel] fix and cleanup device mapper bioset initialization Christoph Hellwig
2022-06-08 6:34 ` Christoph Hellwig
2022-06-08 6:34 ` [dm-devel] [PATCH 1/4] dm: fix bio_set allocation Christoph Hellwig
2022-06-08 6:34 ` Christoph Hellwig
2022-06-08 6:34 ` [dm-devel] [PATCH 2/4] block: remove bioset_init_from_src Christoph Hellwig
2022-06-08 6:34 ` Christoph Hellwig
2022-06-08 6:34 ` [dm-devel] [PATCH 3/4] dm: unexport dm_get_reserved_rq_based_ios Christoph Hellwig
2022-06-08 6:34 ` Christoph Hellwig
2022-06-08 6:34 ` [dm-devel] [PATCH 4/4] dm: refactor dm_md_mempool allocation Christoph Hellwig
2022-06-08 6:34 ` Christoph Hellwig
2022-06-08 18:16 ` [dm-devel] fix and cleanup device mapper bioset initialization Mike Snitzer
2022-06-08 18:16 ` Mike Snitzer
2022-06-09 4:11 ` Christoph Hellwig [this message]
2022-06-09 4:11 ` Christoph Hellwig
2022-06-09 18:16 ` [dm-devel] " Mike Snitzer
2022-06-09 18:16 ` 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=20220609041149.GA31649@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--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 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.