All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Christopher Lentocha <christopherericlentocha@gmail.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: quirk Acer FA100 for non-uniqueue identifiers
Date: Tue, 18 Feb 2025 08:44:02 -0700	[thread overview]
Message-ID: <Z7Sqwg-pY9Aj3dGh@kbusch-mbp> (raw)
In-Reply-To: <381a838c-bb8a-8e95-c35a-343601cbe8e3@gmail.com>

On Tue, Feb 18, 2025 at 08:59:29AM -0500, Christopher Lentocha wrote:
> 
> In order for two Acer FA100 SSDs to work in one PC (in the case of
> myself, a Lenovo Legion T5 28IMB05), and not show one drive and not
> the other, and sometimes mix up what drive shows up (randomly), these
> two lines of code need to be added, and then both of the SSDs will
> show up and not conflict when booting off of one of them. If you boot
> up your computer with both SSDs installed without this patch, you may
> also randomly get into a kernel panic (if the initrd is not set up) or
> stuck in the initrd "/init" process, it is set up, however, if you do
> apply this patch, there should not be problems with booting or seeing
> both contents of the drive. Tested with the btrfs filesystem with a
> RAID configuration of having the root drive '/' combined to make two
> 256GB Acer FA100 SSDs become 512GB in total storage.

Thanks, applied to nvme-6.14.


      reply	other threads:[~2025-02-18 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 13:59 [PATCH] nvme-pci: quirk Acer FA100 for non-uniqueue identifiers Christopher Lentocha
2025-02-18 15:44 ` Keith Busch [this message]

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=Z7Sqwg-pY9Aj3dGh@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=christopherericlentocha@gmail.com \
    --cc=hch@lst.de \
    --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.