From: Christoph Hellwig <hch@lst.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] nvme: Fix typos
Date: Wed, 30 Jul 2025 18:23:21 +0200 [thread overview]
Message-ID: <20250730162321.GA22255@lst.de> (raw)
In-Reply-To: <20250723202801.2909506-1-helgaas@kernel.org>
On Wed, Jul 23, 2025 at 03:27:51PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Fix typos in comments.
This created multiple rejects. Can you resend against the current
tree? If you don't want to deal with the nvme tree, maybe resend
just before/after rc1?
next prev parent reply other threads:[~2025-07-30 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 20:27 [PATCH] nvme: Fix typos Bjorn Helgaas
2025-07-28 17:51 ` Chaitanya Kulkarni
2025-07-30 16:23 ` Christoph Hellwig [this message]
2025-07-30 17:10 ` Bjorn Helgaas
2025-07-30 17:24 ` Christoph Hellwig
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=20250730162321.GA22255@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).