From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Adrian Bunk <bunk@kernel.org>,
ambx1@neo.rr.com, linux-kernel@vger.kernel.org
Subject: Re: pnp_bus_resume(): inconsequent NULL checking
Date: Thu, 21 Feb 2008 17:18:50 +0100 [thread overview]
Message-ID: <47BDA46A.8050306@keyaccess.nl> (raw)
In-Reply-To: <200802210826.53731.bjorn.helgaas@hp.com>
On 21-02-08 16:26, Bjorn Helgaas wrote:
> I'll push it upstream, but a coverity warning seems like a marginal
> excuse for putting it in 2.6.25. Is there any real reason it can't
> wait until 2.6.26?
No, but we're only at -rc2. Dumb little things such as this needn't wait an
entire development cycle I'd feel but I obviously don't feel strongly about
the issue itself.
Rene.
prev parent reply other threads:[~2008-02-21 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 22:49 pnp_bus_resume(): inconsequent NULL checking Adrian Bunk
2008-02-20 0:00 ` Rene Herman
2008-02-20 16:59 ` Bjorn Helgaas
2008-02-21 5:47 ` Rene Herman
2008-02-21 15:26 ` Bjorn Helgaas
2008-02-21 16:09 ` Adrian Bunk
2008-02-21 16:18 ` Rene Herman [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=47BDA46A.8050306@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.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