From: Vinod Koul <vkoul@kernel.org>
To: John Thomson <git@johnthomson.fastmail.com.au>
Cc: "Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
linux-phy@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] phy: ralink: mt7621-pci: add sentinel to quirks table
Date: Sat, 5 Nov 2022 13:01:32 +0530 [thread overview]
Message-ID: <Y2YRVBMqtSVDum8l@matsya> (raw)
In-Reply-To: <20221104205242.3440388-2-git@johnthomson.fastmail.com.au>
On 05-11-22, 06:52, John Thomson wrote:
> With mt7621 soc_dev_attr fixed to register the soc as a device,
> kernel will experience an oops in soc_device_match_attr
>
> This quirk test was introduced in the staging driver in
> commit 9445ccb3714c ("staging: mt7621-pci-phy: add quirks for 'E2'
> revision using 'soc_device_attribute'"). The staging driver was removed,
> and later re-added in commit d87da32372a0 ("phy: ralink: Add PHY driver
> for MT7621 PCIe PHY") for kernel 5.11
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-11-05 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 20:52 [PATCH 0/2] mt7621 pci & phy-pci fix future oops from soc_device_match_attr John Thomson
2022-11-04 20:52 ` [PATCH 1/2] phy: ralink: mt7621-pci: add sentinel to quirks table John Thomson
2022-11-05 6:24 ` Sergio Paracuellos
2022-11-05 7:31 ` Vinod Koul [this message]
2022-11-04 20:52 ` [PATCH 2/2] PCI: mt7621: " John Thomson
2022-11-05 6:25 ` Sergio Paracuellos
2022-12-05 16:26 ` Lorenzo Pieralisi
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=Y2YRVBMqtSVDum8l@matsya \
--to=vkoul@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=bhelgaas@google.com \
--cc=git@johnthomson.fastmail.com.au \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.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;
as well as URLs for NNTP newsgroup(s).