From: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>
To: Sinan Kaya <okaya@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"okaya@codeaurora.org" <okaya@codeaurora.org>,
"Zheng, Joey" <yu.zheng@hxt-semitech.com>
Subject: Re: [PATCH] PCI: Add HXT vendor ID and ACS quirk
Date: Tue, 6 Nov 2018 01:34:07 +0000 [thread overview]
Message-ID: <946ea4b463a44113b6eb84f6b8e5e3f2@HXTBJIDCEMVIW01.hxtcorp.net> (raw)
In-Reply-To: bcaf1d5d-23a6-d4e6-08e8-587daf6cca06@kernel.org
Hi, Sinan,
On 2018/11/6 7:12, Sinan Kaya wrote:
> On 11/4/2018 7:15 PM, Shunyong Yang wrote:
>> Add the HXT vendor ID to pci_ids.h and use it in quirks. As the
>> design of HXT SD4800 ACS feature is the same as QCOM QDF2xxx,
>> pci_quirk_qcom_rp_acs() is reused for SD4800 quirk.
>>
>> Cc: Joey Zheng<yu.zheng@hxt-semitech.com>
>> Signed-off-by: Shunyong Yang<shunyong.yang@hxt-semitech.com>
>
> There is also a couple of hotplug quirks for QDF2400. You should
> probably take care of those as well.
>
> Assuming your PCI IDs are correct:
>
> Reviewed-by: Sinan Kaya <okaya@kernel.org>
>
Thanks for your review and information. I will check the changes.
Shunyong.
next prev parent reply other threads:[~2018-11-06 1:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 3:15 [PATCH] PCI: Add HXT vendor ID and ACS quirk Shunyong Yang
2018-11-05 23:12 ` Sinan Kaya
2018-11-06 1:34 ` Yang, Shunyong [this message]
2018-11-07 7:24 ` [PATCH v2 1/2] " Shunyong Yang
2019-02-01 23:19 ` Bjorn Helgaas
2019-02-11 0:52 ` Yang, Shunyong
2022-02-10 22:53 ` Bjorn Helgaas
2018-11-07 7:25 ` [PATCH v2 2/2] PCI: pciehp: Add HXT quirk for Command Completed errata Shunyong Yang
2018-11-19 1:07 ` Yang, Shunyong
2018-12-07 2:31 ` Yang, Shunyong
2018-11-19 16:16 ` Keith Busch
2018-11-20 10:19 ` Yang, Shunyong
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=946ea4b463a44113b6eb84f6b8e5e3f2@HXTBJIDCEMVIW01.hxtcorp.net \
--to=shunyong.yang@hxt-semitech.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=okaya@kernel.org \
--cc=yu.zheng@hxt-semitech.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).