From: Harry Ciao <qingtao.cao@windriver.com>
To: Greg KH <greg@kroah.com>
Cc: jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [v1 PATCH 1/1] PCI: Add AMD8111 PCI Bridge PCI Device ID
Date: Tue, 10 Mar 2009 09:26:12 +0800 [thread overview]
Message-ID: <49B5C1B4.4040309@windriver.com> (raw)
In-Reply-To: <20090309194306.GC15011@kroah.com>
Hi Greg,
Please see my answers below.
Greg KH 写道:
> On Mon, Mar 09, 2009 at 05:09:03PM +0800, Harry Ciao wrote:
>
>> Add the PCI Device ID for the PCI Bridge Controller on AMD8111 chip,
>> which is used by AMD8111 EDAC driver.
>>
>
> Where is the corrisponding change to the edac driver to use this new id?
>
>
This new id is to be used in the newly added edac driver amd8111_edac.c
that I have posted to the mailing list on March 9th, it is used to probe
the PCI Bridge Controller on AMD8111 chip.
> And for ids that are only in one driver, there is no need to add them to
> the pci_ids.h file. This is what we have been doing for the past few
> years in order to cut down on the merge-mess in the pci_ids.h file for
> no reason.
>
> thanks,
>
> greg k-h
>
>
Ok, I see for the time being I had better define this new id as a macro
in amd8111_edac.c.
And I am a little curious that do you mean that pci_ids.h maintainer
would have to track how many times a new id have been requested to
decide if to merge it into the file or not?
Thank you very much for your comments!
Best regards,
Harry
next prev parent reply other threads:[~2009-03-10 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 9:09 [v1 PATCH 0/1] PCI: Add PCI Device ID for the PCI Bridge Controller on AMD8111 chip Harry Ciao
2009-03-09 9:09 ` [v1 PATCH 1/1] PCI: Add AMD8111 PCI Bridge PCI Device ID Harry Ciao
2009-03-09 19:43 ` Greg KH
2009-03-10 1:26 ` Harry Ciao [this message]
2009-03-11 4:32 ` Greg KH
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=49B5C1B4.4040309@windriver.com \
--to=qingtao.cao@windriver.com \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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