From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Matt Mackall <mpm@selenic•com>
Subject: linux-next: crypto-current tree build warning
Date: Mon, 1 Feb 2010 11:07:09 +1100 [thread overview]
Message-ID: <20100201110709.9de06b42.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hi Herbert,
Today's linux-next build (x86_64 allmodconfig) produced this warning:
drivers/char/random.c: In function 'random_write':
drivers/char/random.c:1104: warning: unused variable 'inode'
Introduced by commit b9b06a1fda275559492f8b083927fde4cec641dc ("random:
drop weird m_time/a_time manipulation") which removed the last usage of
"inode".
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-02-01 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 0:07 Stephen Rothwell [this message]
2010-02-01 10:48 ` linux-next: crypto-current tree build warning Herbert Xu
2010-02-01 23:21 ` Stephen Rothwell
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=20100201110709.9de06b42.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpm@selenic$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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