From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Frans Pop <elendil@planet.nl>
Cc: David John <davidjon@xenontk.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
yinghai@kernel.org
Subject: Re: [PATCH v2] Remove Spurious PnP Memory Reserved Warning
Date: Thu, 6 Aug 2009 14:41:12 -0700 [thread overview]
Message-ID: <20090806144112.77752665@jbarnes-g45> (raw)
In-Reply-To: <200908011256.11628.elendil@planet.nl>
On Sat, 1 Aug 2009 12:56:10 +0200
Frans Pop <elendil@planet.nl> wrote:
> On Tuesday 28 July 2009, Jesse Barnes wrote:
> > I'm inclined to keep the message, since it's just a dev_info and
> > does provide interesting info sometimes. So unless Linus wants to
> > kill it...
>
> Jesse, what do you think of the less invasive patch I suggested in
> http://lkml.org/lkml/2009/7/24/16?
I like it a bit better since it preserves the info in the case where a
resource was already reserved, so I'm fine if it goes upstream. We're
just talking about debug info here so most users shouldn't notice
either unless there's a real problem.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-08-06 21:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 2:44 Linux 2.6.31-rc4 Linus Torvalds
2009-07-23 14:14 ` Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-23 14:42 ` Yinghai Lu
2009-07-23 15:57 ` Jesse Barnes
2009-07-23 14:53 ` Frans Pop
2009-07-23 16:12 ` Linus Torvalds
2009-07-23 16:29 ` Linus Torvalds
2009-07-24 4:34 ` David John
2009-07-24 5:51 ` Kind of like the following. Apply if you feel it is ok to _not_ David John
2009-07-24 7:53 ` [PATCH?] Re: Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-24 6:11 ` [PATCH] Remove Spurious PnP Memory Reserved Warning David John
2009-07-25 7:12 ` David John
2009-07-28 4:06 ` [PATCH v2] " David John
2009-07-28 16:31 ` Jesse Barnes
2009-07-29 6:42 ` David John
2009-08-01 10:56 ` Frans Pop
2009-08-06 21:41 ` Jesse Barnes [this message]
2009-07-23 17:21 ` Linux 2.6.31-rc4 Krzysztof Olędzki
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=20090806144112.77752665@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=davidjon@xenontk.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/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