From: Theodore Ts'o <tytso@mit.edu>
To: kernel-janitors@vger.kernel.org
Subject: Re: [random:dev 2/9] drivers/char/random.c:682:62: sparse: Using plain integer as NULL pointer
Date: Fri, 06 Jul 2012 18:07:35 +0000 [thread overview]
Message-ID: <20120706180735.GE10798@thunk.org> (raw)
In-Reply-To: <20120706173117.GA21914@localhost>
On Sat, Jul 07, 2012 at 01:31:17AM +0800, wfg@linux.intel.com wrote:
> Hi Theodore,
>
> Some trivial sparse warnings :)
Thanks, I'll get these fixed up in the next spin of these patches.
- Ted
prev parent reply other threads:[~2012-07-06 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 17:31 [random:dev 2/9] drivers/char/random.c:682:62: sparse: Using plain integer as NULL pointer wfg
2012-07-06 18:07 ` Theodore Ts'o [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=20120706180735.GE10798@thunk.org \
--to=tytso@mit.edu \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.