From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 2/3] nvme-keyring: typo in nvme_dhchap_psk_lookup()
Date: Fri, 3 Oct 2025 15:12:29 +0200 [thread overview]
Message-ID: <20251003131229.GA18230@lst.de> (raw)
In-Reply-To: <aN_Ek04e4ldw7Ppq@kbusch-mbp>
On Fri, Oct 03, 2025 at 02:41:55PM +0200, Keith Busch wrote:
> On Fri, Oct 03, 2025 at 09:35:06AM +0200, Christoph Hellwig wrote:
> > On Wed, Oct 01, 2025 at 04:21:59PM +0200, Hannes Reinecke wrote:
> > > Spurious semicolon in the function stub nvme_dhchap_psk_lookup().
> > >
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202509302259.Yku13u90-lkp@intel.com/
> > > Signed-off-by: Hannes Reinecke <hare@kernel.org>
> >
> > Looks good. But maybe we should just drop the series and pick up a
> > resend with the fixes folded in?
>
> Yes, I was totally planning to squash and force push, but I'm
> considering moving this to the -6.19 branch rather than the current
> window.
Yeah, the 6.18 merge window is over.
next prev parent reply other threads:[~2025-10-03 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:21 [PATCH 0/3] nvme: kbuild robot fixes Hannes Reinecke
2025-10-01 14:21 ` [PATCH 1/3] nvme-keyring: use correct format specifier Hannes Reinecke
2025-10-03 7:34 ` Christoph Hellwig
2025-10-06 14:18 ` Keith Busch
2025-10-01 14:21 ` [PATCH 2/3] nvme-keyring: typo in nvme_dhchap_psk_lookup() Hannes Reinecke
2025-10-03 7:35 ` Christoph Hellwig
2025-10-03 12:41 ` Keith Busch
2025-10-03 13:12 ` Christoph Hellwig [this message]
2025-10-01 14:22 ` [PATCH 3/3] nvme-auth: move declaration of nvme_auth_extract_key() Hannes Reinecke
2025-10-03 7:35 ` 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=20251003131229.GA18230@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--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).