public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warning after merge of the random tree
Date: Mon, 21 Jul 2014 17:49:13 +1000	[thread overview]
Message-ID: <20140721174913.09d5de01@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 428 bytes --]

Hi Ted,

After merging the random tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/char/random.c: In function 'SYSC_getrandom':
drivers/char/random.c:1526:6: warning: unused variable 'r' [-Wunused-variable]
  int r;
      ^

Introduced by commit 386474e168a8 ("random: introduce getrandom(2) system call").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-07-21  7:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  7:49 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-02  3:44 linux-next: build warning after merge of the random tree Stephen Rothwell
2020-03-06  4:53 ` Stephen Rothwell
2020-03-10 12:17   ` Mark Rutland
2020-03-10 14:46     ` Theodore Y. Ts'o
2020-03-16  5:59       ` Stephen Rothwell
2020-03-19  3:30         ` Theodore Y. Ts'o
2018-07-16  5:52 Stephen Rothwell
2018-06-08  3:37 Stephen Rothwell
2018-06-18  3:35 ` Stephen Rothwell
2018-06-18  5:29   ` Tobin C. Harding
2018-07-10  7:26     ` Stephen Rothwell
2017-02-01  6:09 Stephen Rothwell
2013-09-23  4:39 Stephen Rothwell
2013-09-23  4:42 ` 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=20140721174913.09d5de01@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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