From: Lukas Wunner <lukas@wunner.de>
To: Ricky WU <ricky_wu@realtek.com>
Cc: "scott@spiteful.org" <scott@spiteful.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [bug report] nvme not re-recognize when changed M.2 SSD in S3 mode
Date: Wed, 15 May 2024 10:46:47 +0200 [thread overview]
Message-ID: <ZkR2d0xp9q90bgLx@wunner.de> (raw)
In-Reply-To: <7cd910060f3d4951ac0edd92910a55c2@realtek.com>
On Wed, May 15, 2024 at 07:31:05AM +0000, Ricky WU wrote:
> > I tested this patch and the result looks good, but if the two SSD has
> > same VID, PID and capacity it still has problem.
> > So I think add S/N to compare is necessary if it can do
> >
> > And I also tested SD7.0 card the result is same with M.2 SSD
>
> May I know the related patch has upstream schedule?
Sorry for the delay, I've been stretched a bit thin between
PCI device authentication and solving a Thunderbolt issue.
The merge window opened 2 days ago and it doesn't really
make sense to submit something until it closes and v6.10-rc1
is released on May 26.
I intend to rework this patch based on your feedback and
re-submit shortly after the merge window closes.
Thanks!
Lukas
prev parent reply other threads:[~2024-05-15 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 5:44 [bug report] nvme not re-recognize when changed M.2 SSD in S3 mode Ricky WU
2024-04-09 13:16 ` Bjorn Helgaas
2024-04-10 10:07 ` Lukas Wunner
2024-04-10 14:58 ` Lukas Wunner
2024-04-25 6:02 ` Ricky WU
2024-05-27 11:54 ` Lukas Wunner
2024-05-29 7:47 ` Ricky WU
2024-05-29 14:43 ` Lukas Wunner
2024-05-15 7:31 ` Ricky WU
2024-05-15 8:46 ` Lukas Wunner [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=ZkR2d0xp9q90bgLx@wunner.de \
--to=lukas@wunner.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ricky_wu@realtek.com \
--cc=scott@spiteful.org \
/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.