public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	lm-sensors <lm-sensors@lm-sensors.org>, Greg KH <greg@kroah.com>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH 2/5] i5k_amb: Load automatically on all 5000/5400 chipsets
Date: Sat, 8 Nov 2008 12:09:50 +0100	[thread overview]
Message-ID: <20081108120950.397a3165@hyperion.delvare> (raw)
In-Reply-To: <20081107185631.13022.59600.stgit@elm3a70.beaverton.ibm.com>

Hi Darrick,

On Fri, 07 Nov 2008 10:56:31 -0800, Darrick J. Wong wrote:
> It turns out that we cannot create a pci_driver in this driver because PCI will
> not call this module's probe function if the i5000-edac driver is already
> loaded.

I seem to recall work in progress to let multiple drivers bind to the
same PCI device. Greg, Kay, what's the status?

> That said, we only want one value (AMBASE) from the PCI config space.
> Neither driver alters this value, so it's safe to read it.  However, we still
> want the module aliases, so provide that.
> 
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> ---
> 
>  drivers/hwmon/i5k_amb.c |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/hwmon/i5k_amb.c b/drivers/hwmon/i5k_amb.c
> index 2ede938..a3fa639 100644
> --- a/drivers/hwmon/i5k_amb.c
> +++ b/drivers/hwmon/i5k_amb.c
> @@ -490,6 +490,14 @@ static unsigned long chipset_ids[] = {
>  	0
>  };
>  
> +static struct pci_device_id i5k_amb_ids[] __devinitdata = {
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_5000_ERR) },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_5400_ERR) },
> +	{ 0, },
> +};
> +
> +MODULE_DEVICE_TABLE(pci, i5k_amb_ids);
> +
>  static int __devinit i5k_amb_probe(struct platform_device *pdev)
>  {
>  	struct i5k_amb_data *data;
> 

Looks good to me, we can apply this for now.

Acked-by: Jean Delvare <khali@linux-fr.org>

-- 
Jean Delvare

  reply	other threads:[~2008-11-08 11:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 18:56 [PATCH 0/5] Various hwmon patches Darrick J. Wong
2008-11-07 18:56 ` [PATCH 1/5] adt7462: New hwmon driver Darrick J. Wong
2008-11-07 19:04   ` Harvey Harrison
2008-11-07 19:27     ` Andrew Morton
2008-11-07 19:34       ` Darrick J. Wong
2008-11-07 19:38     ` Darrick J. Wong
2008-11-07 19:18   ` Andrew Morton
2008-11-07 18:56 ` [PATCH 2/5] i5k_amb: Load automatically on all 5000/5400 chipsets Darrick J. Wong
2008-11-08 11:09   ` Jean Delvare [this message]
2008-11-11  6:26     ` Greg KH
2008-11-07 18:56 ` [PATCH 3/5] adt7470: Check input range when sysfs files are written Darrick J. Wong
2008-11-11  0:22   ` Andrew Morton
2008-11-11  0:49     ` Darrick J. Wong
2008-11-07 18:56 ` [PATCH 4/5] adt7473: Check inputs from sysfs writes Darrick J. Wong
2008-11-07 19:20   ` Andrew Morton
2008-11-07 20:35     ` Jean Delvare
2008-11-07 20:49     ` Joe Perches
2008-11-07 21:00       ` Jean Delvare
2008-11-07 21:02         ` Randy Dunlap
2008-11-07 18:56 ` [PATCH 5/5] lm85: Support adt7468 chips Darrick J. Wong

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=20081108120950.397a3165@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=djwong@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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