All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>, Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	"linux-pci" <linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: [PATCH] PCI: fix ICH6 quirks
Date: Sat, 19 Aug 2006 00:03:17 +0200	[thread overview]
Message-ID: <20060819000317.198c3c54.khali@linux-fr.org> (raw)
In-Reply-To: <200608181921.31798.daniel.ritz-ml@swissonline.ch>

> On Friday 18 August 2006 18.57, Jean Delvare wrote:
> > Hi Daniel,
> > 
> > > [PATCH] PCI: fix ICH6 quirks
> > > 
> > > - add the ICH6(R) LPC to the ICH6 ACPI quirks. currently only the ICH6-M is
> > >   handled. [ PCI_DEVICE_ID_INTEL_ICH6_1 is the ICH6-M LPC, ICH6_0 is the ICH6(R) ]
> > 
> > No objection.
> > 
> > > - remove the wrong quirk calling asus_hides_smbus_lpc() for ICH6. the register
> > >   modified in asus_hides_smbus_lpc() has a different meaning in ICH6.
> > 
> > My mistake :( Thanks for fixing it. Do you know if executing the old
> > quirk on the ICH6 can cause trouble? In other words, should we backport
> > this fix to 2.6.17.y?
> 
> the register it touches is part of the "root complex base address" register. so
> changing it means the ICH6 decodes a different address range that could conflict
> with something else...so yes, i think this is a 2.6.17.x candidate.

OK, this also means that we want your patch in 2.6.18. Greg, can you
pick it quickly?

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2006-08-18 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 14:50 [PATCH] PCI: fix ICH6 quirks Daniel Ritz
2006-08-18 16:57 ` Jean Delvare
2006-08-18 17:21   ` Daniel Ritz
2006-08-18 22:03     ` Jean Delvare [this message]
2006-08-21 18:25 ` 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=20060819000317.198c3c54.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=akpm@osdl.org \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.