All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christopher Lentocha <christopherericlentocha@gmail.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix two Acer FA100 SSDs from interfering in one PC
Date: Tue, 18 Feb 2025 09:42:18 +0100	[thread overview]
Message-ID: <20250218084217.GA11129@lst.de> (raw)
In-Reply-To: <71ea150b-9ea0-3e49-6195-ebbe761bacb1@gmail.com>

The subject line should rwad something like:

nvme-pci: quirk Acer FA100 for non-uniqueue identifiers

and the commit log should be wrapped to 73 characters.

Otherwise this looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

and we can probably just fix that up when applying the patch.



  reply	other threads:[~2025-02-18  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 13:24 [PATCH] Fix two Acer FA100 SSDs from interfering in one PC Christopher Lentocha
2025-02-18  8:42 ` Christoph Hellwig [this message]
2025-02-18 13:59   ` Christopher Lentocha

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=20250218084217.GA11129@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=christopherericlentocha@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.