Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurence Oberman <loberman@redhat.com>
To: Maurizio Lombardi <mlombard@redhat.com>, kbusch@kernel.org
Cc: linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de,
	dwagner@suse.de
Subject: Re: [PATCH 0/2] Fix for nvme quirks module parameter
Date: Fri, 23 Oct 2026 10:01:13 -0400	[thread overview]
Message-ID: <41702ce74457dec608620f4b5ba9e7ff5ab482d8.camel@redhat.com> (raw)
In-Reply-To: <20261023094806.944563-1-mlombard@redhat.com>

On Fri, 2026-10-23 at 11:48 +0200, Maurizio Lombardi wrote:
> The first patch fixes a boot hang when nvme-pci is built-in in the
> kernel, reported by Ramon Jesus Miranda here:
> https://lore.kernel.org/linux-nvme/20261018155426.1299676-1-ramonjesusmiranda@gmail.com/
> 
> The second patch increases the quirks parameter's buffer.
> 
> Maurizio Lombardi (2):
>   nvme-pci: fix early boot hang with nvme.quirks= parameter
>   nvme-pci: increase quirks_param buffer size to 256 bytes
> 
>  drivers/nvme/host/pci.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Unless I am missing something, this looks good to me and i know it was
already tested.

For the series
Reviewed-by: Laurence Oberman <loberman@redhat.com>



  parent reply	other threads:[~2026-10-23 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  9:48 [PATCH 0/2] Fix for nvme quirks module parameter Maurizio Lombardi
2026-10-23  9:48 ` [PATCH 1/2] nvme-pci: fix early boot hang with nvme.quirks parameter Maurizio Lombardi
2026-10-23  9:48 ` [PATCH 2/2] nvme-pci: increase quirks_param buffer size to 256 bytes Maurizio Lombardi
2026-10-23 14:01 ` Laurence Oberman [this message]
2026-10-23 22:06 ` [PATCH 0/2] Fix for nvme quirks module parameter Keith Busch

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=41702ce74457dec608620f4b5ba9e7ff5ab482d8.camel@redhat.com \
    --to=loberman@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dwagner@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@redhat.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