public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Miquel van Smoorenburg <mikevs@xs4all.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.26-rc: x86: pci-dma.c: use __GFP_NO_OOM instead of __GFP_NORETRY
Date: Thu, 26 Jun 2008 13:38:55 +0200	[thread overview]
Message-ID: <20080626113855.GE29619@elte.hu> (raw)
In-Reply-To: <200806101014.25089.jbarnes@virtuousgeek.org>


* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Tuesday, June 10, 2008 3:23 am Ingo Molnar wrote:
> > * Miquel van Smoorenburg <mikevs@xs4all.net> wrote:
> > > On Mon, 2008-06-02 at 12:15 +0200, Ingo Molnar wrote:
> > > > * Miquel van Smoorenburg <mikevs@xs4all.net> wrote:
> > > > > Okay, so how about this then ?
> > > >
> > > > applied to tip/pci-for-jesse for more testing. Thanks,
> > >
> > > I've thought about it a bit more, and I think the actual patch that
> > > really does what everybody wants is this one instead:
> >
> > applied a delta patch version of the one below to tip/pci-for-jesse.
> 
> Speaking of that branch, how do you want to handle it?  Is it intended 
> for my linux-next branch or are some of the fixes important to get 
> upstream now?  Which branch should I diff/log against to see the 
> changes (last time I looked it appeared neither master nor tip were 
> the correct ones...)

that branch is always based in -git so if stuff goes upstream patches 
disappear from it. git-log linus/master..tip/pci-for-jesse should tell 
the currently pending items. Right now it's just two lowprio items:

 Yinghai Lu (2):
      pci: debug extra pci resources range
      pci: debug extra pci bus resources

	Ingo

  parent reply	other threads:[~2008-06-26 11:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 23:49 [PATCH] 2.6.26-rc: x86: pci-dma.c: use __GFP_NO_OOM instead of __GFP_NORETRY Miquel van Smoorenburg
2008-05-27  8:03 ` Ingo Molnar
2008-05-27  8:47 ` Andrew Morton
2008-05-27  9:35   ` Miquel van Smoorenburg
2008-05-28  2:47   ` Andi Kleen
2008-05-28  8:31     ` Miquel van Smoorenburg
2008-05-28  8:40       ` Andrew Morton
2008-05-28 12:54         ` Andi Kleen
2008-06-02 10:15       ` Ingo Molnar
     [not found]         ` <1212682484.4332.7.camel@n2o.xs4all.nl>
2008-06-10 10:23           ` Ingo Molnar
2008-06-10 17:14             ` Jesse Barnes
2008-06-11 14:26               ` Miquel van Smoorenburg
2008-06-26 11:38               ` Ingo Molnar [this message]
2008-07-02  2:39                 ` Jesse Barnes
2008-07-02  2:46                   ` Yinghai Lu
2008-07-02  2:48                     ` 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=20080626113855.GE29619@elte.hu \
    --to=mingo@elte.hu \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikevs@xs4all.net \
    /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