From: Yinghai Lu <yinghai@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 4/7] x86/pci: use u64 instead of size_t in amd_bus.c -v2
Date: Fri, 15 Jan 2010 13:18:30 -0800 [thread overview]
Message-ID: <4B50DBA6.8070406@kernel.org> (raw)
In-Reply-To: <20100115114928.5e565e30@jbarnes-piketon>
On 01/15/2010 11:49 AM, Jesse Barnes wrote:
> On Fri, 18 Dec 2009 12:09:45 -0800
> Yinghai Lu <yinghai@kernel.org> wrote:
>
>>
>> prepare to enable it for 32bit
>>
>> -v2: remove not needed cast
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>
> 4-6 have conflicts against my linux-next branch, can you refresh them?
because it will rely on range.c related cleanup. can we make it go through tip
and add acked-by from you?
Thanks
Yinghai
next prev parent reply other threads:[~2010-01-15 21:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B2BE063.4040704@kernel.org>
2009-12-18 20:09 ` [PATCH 1/7] x86/pci: intel ioh bus num reg accessing fix Yinghai Lu
2009-12-18 20:09 ` [PATCH 2/7] x86/pci: use resource_size_t in update_res -v2 Yinghai Lu
2010-01-15 19:49 ` Jesse Barnes
2010-01-15 21:20 ` Yinghai Lu
2010-01-15 21:39 ` Jesse Barnes
2010-01-22 1:55 ` Yinghai Lu
2010-01-25 18:49 ` Jesse Barnes
2009-12-18 20:09 ` [PATCH 3/7] x86/pci: amd one chain system to use pci read out res Yinghai Lu
2009-12-18 20:09 ` [PATCH 4/7] x86/pci: use u64 instead of size_t in amd_bus.c -v2 Yinghai Lu
2010-01-15 19:49 ` Jesse Barnes
2010-01-15 21:18 ` Yinghai Lu [this message]
2009-12-18 20:09 ` [PATCH 5/7] x86/pci: add cap_resource -v2 Yinghai Lu
2009-12-18 20:09 ` [PATCH 6/7] x86/pci: enable pci root res read out for 32bit too -v3 Yinghai Lu
2009-12-18 20:09 ` [PATCH 7/7] x86/pci: don't check mmconf again if it is from MSR with amd faml0h Yinghai Lu
2010-01-15 19:42 ` Jesse Barnes
2010-01-15 21:16 ` Yinghai Lu
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=4B50DBA6.8070406@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.