From: Eric Sandeen <sandeen@redhat.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: fs/hfs/btree.c: new NULL dereference
Date: Mon, 14 Jan 2008 15:35:52 -0600 [thread overview]
Message-ID: <478BD5B8.1010805@redhat.com> (raw)
In-Reply-To: <20080114211305.GI9847@does.not.exist>
Adrian Bunk wrote:
> The Coverity checker spotted the following NULL dereference introduced
> by commit cf0594625083111ae522496dc1c256f7476939c2:
Oops. Thanks, Adrian.
Patch sent on a different thread, following another fixup patch for
Roman - you're cc'd.
Thanks,
-Eric
prev parent reply other threads:[~2008-01-14 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 21:13 fs/hfs/btree.c: new NULL dereference Adrian Bunk
2008-01-14 21:35 ` Eric Sandeen [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=478BD5B8.1010805@redhat.com \
--to=sandeen@redhat.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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