From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
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: Wed, 10 Sep 2008 20:08:21 +0200 [thread overview]
Message-ID: <20080910180821.GA6864@elte.hu> (raw)
In-Reply-To: <200809101048.57119.jbarnes@virtuousgeek.org>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Wednesday, September 10, 2008 1:44 am Ingo Molnar wrote:
> > * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > > print out for Device BAR address before kernel try to update them.
> > >
> > > also change it to KERN_DEBUG instead...
> > >
> > > v2: update to linux-pci next
> > > also add (unsigned long long) cast
> > >
> > > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
> >
> > Jesse, if you want to pick it up, could we please do this via git
> > methods (git-pull and stuff)? The commit below is the one in -tip -
> > should i separate it out?
>
> Sure, though I'm not sure why I shouldn't just be applying this stuff
> to my tree first... Seems weird to pull from you only to then ask
> Linus to pull.
sure - it's just that it all happened weeks ago so it's intermixed. As
long as you dont mind the duplicate commit (git will sort it out fine)
we can apply it to both trees.
Ingo
next prev parent reply other threads:[~2008-09-10 18:08 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 [this message]
2008-09-10 18:23 ` Jesse Barnes
2008-09-11 7:56 ` Ingo Molnar
2008-09-11 16:43 ` Jesse Barnes
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=20080910180821.GA6864@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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