mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"Brown, Len" <len.brown@intel.com>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] PCI changes for 2.6.33
Date: Mon, 14 Dec 2009 12:51:54 +0800	[thread overview]
Message-ID: <1260766314.3834.3.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0912111216431.3560@localhost.localdomain>

On Sat, 2009-12-12 at 04:22 +0800, Linus Torvalds wrote:
> 
> On Fri, 11 Dec 2009, Jesse Barnes wrote:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 linux-next
> > 
> > I've got a section mismatch in here, but the fix will be part of the next
> > pull req (updated patch just came in recently).
> > 
> > Probably the biggest change here (at least my change count) is Bjorn's
> > MMCONFIG rework.  It sets the stage for hot plugging of host bridges and
> > _CBA and includes some nice cleanups besides.
> 
> Ok, so I got a few conflicts with the iommu/dmar changes (ACS related 
> changes versus the iommu_init changes) and with the ACPICA update 
> (acpi_walk_namespace() change in acpiphp_glue - it now takes a post-order 
> callback too).
> 
> I resolved them all, hopefully even correctly, but people should look over 
> the end result.

I checked all calls of acpi_walk_namespace in
drivers/pci/hotplug/acpiphp_glue.c.
All are correct.

Thanks,
Lin Ming


      reply	other threads:[~2009-12-14  5:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 19:02 Jesse Barnes
2009-12-11 20:22 ` Linus Torvalds
2009-12-14  4:51   ` Lin Ming [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=1260766314.3834.3.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jbarnes@virtuousgeek.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome