From: Alex Chiang <achiang@hp.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
David Woodhouse <David.Woodhouse@intel.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pci related patches 11-21-2009
Date: Tue, 24 Nov 2009 21:45:17 -0700 [thread overview]
Message-ID: <20091125044517.GA3861@ldl.fc.hp.com> (raw)
In-Reply-To: <4B0C9382.9010100@kernel.org>
* Yinghai Lu <yinghai@kernel.org>:
> Jesse Barnes wrote:
> >
> > I commented on one of the resource patches, I'll check the
> > other two (long standing leaf release and pciehp) ones again;
> > I mainly want a bunch of tested-bys for those.
>
> thanks. thought will get one Reviewed-by and Tested-by from
> Kenji. still need to address bridges resource shrink hotplug
> bridges other than pcie. already sent him one add-on patch.
Sorry, I have been swamped lately with other things.
I will try and test Yinghai's patches this week.
/ac
prev parent reply other threads:[~2009-11-25 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 8:35 pci related patches 11-21-2009 Yinghai Lu
2009-11-21 8:39 ` x86 " Yinghai Lu
2009-11-23 11:51 ` [tip:x86/apic] x86: apic: Remove not needed #ifdef tip-bot for Yinghai Lu
2009-11-23 11:52 ` [tip:x86/apic] x86: Re-get cfg_new in case reuse/move irq_desc tip-bot for Yinghai Lu
2009-11-23 11:52 ` [tip:x86/apic] x86: apic: Print out SRAT table APIC id in hex tip-bot for Yinghai Lu
2009-11-23 11:52 ` [tip:x86/mm] x86, numa, bootmem: Only free bootmem on NUMA failure path tip-bot for Yinghai Lu
2009-11-23 11:52 ` [tip:x86/mm] x86, numa: Use near(er) online node instead of roundrobin for NUMA tip-bot for Yinghai Lu
2009-12-16 2:06 ` x86 related patches 12-15-2009 Yinghai Lu
2009-11-24 21:26 ` pci related patches 11-21-2009 Jesse Barnes
2009-11-25 2:16 ` Yinghai Lu
2009-11-25 4:45 ` Alex Chiang [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=20091125044517.GA3861@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=David.Woodhouse@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@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 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.