From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme updates for Linux 5.19
Date: Wed, 18 May 2022 09:33:46 +0200 [thread overview]
Message-ID: <5ed3aa33-7188-4d84-218a-ae1a50af0ebf@suse.de> (raw)
In-Reply-To: <YoSf2UvYcW9fHebf@infradead.org>
On 5/18/22 09:27, Christoph Hellwig wrote:
> On Wed, May 18, 2022 at 09:23:45AM +0200, Hannes Reinecke wrote:
>> On 5/18/22 08:47, Christoph Hellwig wrote:
>>> The following changes since commit c23d47abee3a54e4991ed3993340596d04aabd6a:
>>>
>>> loop: remove most the top-of-file boilerplate comment from the UAPI header (2022-05-10 06:30:05 -0600)
>>>
>> Hmm. So how do we progress with the authentication patches?
>> Shall I resubmit them?
>> Will you be picking them up?
>> Is there anything I need to fix up?
>
> I'm a little worried adding it this late in the cycle, especially with
> the (although rather trivial) crypto patches not having any reviews from
> the crypto maintainers. If you can get those we should be ready early
> for the next merge window which is going to start in just a few days.
Right. Will see what I can do.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
next prev parent reply other threads:[~2022-05-18 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:47 [GIT PULL] nvme updates for Linux 5.19 Christoph Hellwig
2022-05-18 7:23 ` Hannes Reinecke
2022-05-18 7:27 ` Christoph Hellwig
2022-05-18 7:33 ` Hannes Reinecke [this message]
2022-05-18 12:28 ` 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=5ed3aa33-7188-4d84-218a-ae1a50af0ebf@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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