From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] pci: fix merging left out for BAR print out v2
Date: Thu, 11 Sep 2008 09:43:20 -0700 [thread overview]
Message-ID: <200809110943.20596.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080911075623.GA5500@elte.hu>
On Thursday, September 11, 2008 12:56 am Ingo Molnar wrote:
> > Ah I see, sure I can pull your bits. /me gets out his breadcrumbs in
> > preparation for entering the x86 forest. Does your -tip just contain
> > stuff you're sending to Linus for 2.6.27?
>
> no, the .27 buckets of -tip are almost completely emptied - we are in
> the final stages of .27 stabilization. -tip includes all the v2.6.28
> bits. (which this patch would be too IMHO)
>
> anyway, there's no big issue here i think, upstream -git is fine i
> think, please apply the patch to your tree (it only changes printouts),
> it should not cause any big conflicts.
I was thinking it would be good to have this in 2.6.27 since it's a regression
vs. earlier kernels. Anyway I'll apply the patch and let git sort out the
duplication.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2008-09-11 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:27 [PATCH] pci: fix merging left out for BAR print out v2 Yinghai Lu
2008-09-10 8:44 ` Ingo Molnar
2008-09-10 17:48 ` Jesse Barnes
2008-09-10 18:01 ` Yinghai Lu
2008-09-10 18:08 ` Ingo Molnar
2008-09-10 18:23 ` Jesse Barnes
2008-09-11 7:56 ` Ingo Molnar
2008-09-11 16:43 ` Jesse Barnes [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=200809110943.20596.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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