From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for Linux 6.9
Date: Thu, 2 May 2024 07:46:07 -0600 [thread overview]
Message-ID: <b34db4f2-9f95-4426-9d0d-d99abedc896b@kernel.dk> (raw)
In-Reply-To: <ZjOOa7KiIGnOjlDM@kbusch-mbp.dhcp.thefacebook.com>
On 5/2/24 7:00 AM, Keith Busch wrote:
> Jens:
>
> I am on travel right now, and I've lost communication with my remote
> server with my signing and push keys; therefore this does not have a
> tag, much less a signed one. Since nvme is a bit behind on our pull
> requests, I would like to get this out before the next rc. You can ping
> me on back channel if you want to verify the legitimacy of the pull.
Verified out-of-band - thanks, pulled!
--
Jens Axboe
next prev parent reply other threads:[~2024-05-02 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 13:00 [GIT PULL] nvme fixes for Linux 6.9 Keith Busch
2024-05-02 13:46 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 17:48 Keith Busch
2024-05-09 17:50 ` Jens Axboe
2024-04-04 16:59 Keith Busch
2024-04-04 19:23 ` 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=b34db4f2-9f95-4426-9d0d-d99abedc896b@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).