All of lore.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 Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Tobin C. Harding" <me@tobin.cc>
Subject: Re: linux-next: build warning after merge of the random tree
Date: Mon, 18 Jun 2018 13:35:23 +1000	[thread overview]
Message-ID: <20180618133523.30db3ba0@canb.auug.org.au> (raw)
In-Reply-To: <20180608133748.58a272d5@canb.auug.org.au>

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

Hi all,

On Fri, 8 Jun 2018 13:37:48 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the random tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> lib/vsprintf.c:1668:13: warning: 'have_filled_random_ptr_key' defined but not used [-Wunused-variable]
>  static bool have_filled_random_ptr_key __read_mostly;
>              ^~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Introduced by commit
> 
>   bfe80ed3d7c7 ("vsprintf: add command line option debug_boot_weak_hash")

I am still getting this ...
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-06-18  3:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08  3:37 linux-next: build warning after merge of the random tree Stephen Rothwell
2018-06-18  3:35 ` Stephen Rothwell [this message]
2018-06-18  5:29   ` Tobin C. Harding
2018-07-10  7:26     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-03-02  3:44 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
2017-02-01  6:09 Stephen Rothwell
2014-07-21  7:49 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=20180618133523.30db3ba0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=me@tobin.cc \
    --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 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.