mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Build bot for Mark Brown <broonie@kernel.org>,
	kernel-build-reports@lists.linaro.org,
	linux-kernel@vger.kernel.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>
Subject: Re: master build: 0 failures 3 warnings (v4.7-rc3-87-gbb96727)
Date: Fri, 17 Jun 2016 14:10:32 +0200	[thread overview]
Message-ID: <88431021.B13PyGg7Nr@wuerfel> (raw)
In-Reply-To: <E1bDsRz-0004Hi-OI@optimist>

On Friday, June 17, 2016 1:00:40 PM CEST Build bot for Mark Brown wrote:
>           2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]

-stable regression, still not fixed. Stefano applied the patch
into xen-tip/linux-next, but so far it has not shown up into v4.7,
so Greg hasn't had a chance to backport it.

>           1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]

A patch is in linux-next now, my original patch was wrong, but the new
one should work. I suspect this will have to wait for v4.8 though,
as the current code is not broken and the warning has been around
for a long time.

>           1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]

Jonathan Cameron applied my patch to his "fixes-togreg" branch last Saturday,
but it hasn't shown up in linux-next or mainline yet.

	Arnd

           reply	other threads:[~2016-06-17 12:09 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1bDsRz-0004Hi-OI@optimist>]

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=88431021.B13PyGg7Nr@wuerfel \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=jic23@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®