From: Eric Biggers <ebiggers@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Satya Tangirala <satyaprateek2357@gmail.com>,
dm-devel@redhat.com, linux-mmc@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v6 0/4] blk-crypto cleanups
Date: Thu, 21 Oct 2021 09:46:38 -0700 [thread overview]
Message-ID: <YXGZbvTQBgtaPojY@gmail.com> (raw)
In-Reply-To: <YW24UuB8dLWwl9ni@sol.localdomain>
On Mon, Oct 18, 2021 at 11:09:22AM -0700, Eric Biggers wrote:
> On Mon, Oct 18, 2021 at 11:04:49AM -0700, Eric Biggers wrote:
> >
> > This series applies to block/for-next.
> >
> > Changed v5 => v6:
> > - Rebased onto block/for-next yet again
> > - Added more Reviewed-by tags
> >
> > Changed v4 => v5:
> > - Rebased onto block/for-next again
> > - Added Reviewed-by tags
> >
> > Changed v3 => v4:
> > - Rebased onto block/for-next to resolve a conflict due to
> > 'struct request' being moved.
>
> Jens, I keep having to rebase this patchset. Is there anything else you're
> waiting for before applying it for 5.16? Thanks!
>
> - Eric
Ping?
next prev parent reply other threads:[~2021-10-21 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 18:04 [PATCH v6 0/4] blk-crypto cleanups Eric Biggers
2021-10-18 18:04 ` [PATCH v6 1/4] blk-crypto-fallback: properly prefix function and struct names Eric Biggers
2021-10-18 18:04 ` [PATCH v6 2/4] blk-crypto: rename keyslot-manager files to blk-crypto-profile Eric Biggers
2021-10-18 18:04 ` [PATCH v6 3/4] blk-crypto: rename blk_keyslot_manager to blk_crypto_profile Eric Biggers
2021-10-18 18:04 ` [PATCH v6 4/4] blk-crypto: update inline encryption documentation Eric Biggers
2021-10-18 18:09 ` [PATCH v6 0/4] blk-crypto cleanups Eric Biggers
2021-10-21 16:46 ` Eric Biggers [this message]
2021-10-21 16:49 ` Jens Axboe
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=YXGZbvTQBgtaPojY@gmail.com \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyaprateek2357@gmail.com \
/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).