From: Borislav Petkov <bp@alien8.de>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: Wan ZongShun <Vincent.Wan@amd.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Wan ZongShun <linux@mcuos.com>
Subject: Re: [PATCH] SDHCI: Change AMD SDHCI quirk application scope
Date: Fri, 5 Jun 2015 15:52:30 +0200 [thread overview]
Message-ID: <20150605135230.GJ3679@pd.tnic> (raw)
In-Reply-To: <CAKT61h8kN33D03jV7pJ7b25p9M6JSPm2WxLgh4DhJxnteHQnrw@mail.gmail.com>
On Fri, Jun 05, 2015 at 06:01:56PM +0800, Wan ZongShun wrote:
> The KERNCZ is new AMD SB/FCH generation name, like HUDSON2 is old FCH
> generation.
> We will adopt 0x790b as device ID since from this KERNCZ gereration.
True story. Strange name that.
> The i2cpiix4.c driver and eMMC driver both will use this device ID
> macro, Do you think I should submit two patches synchronously? like
> patch1: change i2cpiix4 driver to use PCI_DEVICE_ID_AMD_KERNCZ_SMBUS,
> patch2: for eMMC quirk in sdhci-pci.c?
>
> And then the PCI_DEVICE_ID_AMD_KERNCZ_SMBUS can be go into pci ids.h?
If you have all those patches ready, you could do a first patch adding
the PCI ID to pci_ids.h only.
Then follow with the different driver changes, i.e. sdhci-pci.c,
i2cpiix4, and so on and make it clear in the 0/n message that they all
depend on the first one.
Or something along those lines.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-06-05 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 14:33 [PATCH] SDHCI: Change AMD SDHCI quirk application scope Wan ZongShun
2015-06-04 15:32 ` Borislav Petkov
2015-06-05 1:37 ` Wan ZongShun
2015-06-05 9:20 ` Borislav Petkov
2015-06-05 10:01 ` Wan ZongShun
2015-06-05 13:52 ` Borislav Petkov [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=20150605135230.GJ3679@pd.tnic \
--to=bp@alien8.de \
--cc=Vincent.Wan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@mcuos.com \
--cc=mcuos.com@gmail.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox