From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Miquel van Smoorenburg <mikevs@xs4all.net>,
linux-kernel@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] 2.6.26-rc: x86: pci-dma.c: use __GFP_NO_OOM instead of __GFP_NORETRY
Date: Tue, 1 Jul 2008 19:39:53 -0700 [thread overview]
Message-ID: <200807011939.53427.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080626113855.GE29619@elte.hu>
On Thursday, June 26, 2008 4:38 am Ingo Molnar wrote:
> 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
It looks like these add some new, unconditional debug output? I guess I
shouldn't worry about printks so much at this point, given how much
obsolete/uninteresting info gets dumped these days, but it would be nice if
this were only dumped if some debug option were set. Given the variety of
PCI stuff we might like to dump at various times, maybe it's time we added a
few new pci=debug=foo options? Yinghai?
Thanks,
Jesse
next prev parent reply other threads:[~2008-07-02 2:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 23:49 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
2008-07-02 2:39 ` Jesse Barnes [this message]
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=200807011939.53427.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®