From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel-build-reports@lists.linaro.org,
Build bot for Mark Brown <broonie@kernel.org>,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: v4.4.14 build: 0 failures 1 warnings (v4.4.14)
Date: Sun, 24 Jul 2016 16:59:45 -0700 [thread overview]
Message-ID: <20160724235945.GA23085@kroah.com> (raw)
In-Reply-To: <3979206.RoHYNJ6ueF@wuerfel>
On Sat, Jun 25, 2016 at 11:23:05AM +0200, Arnd Bergmann wrote:
> On Saturday, June 25, 2016 12:37:17 AM CEST Build bot for Mark Brown wrote:
> > Warnings Summary: 1
> > arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
> > 1 ../drivers/xen/balloon.c:155:13: warning:
> > 'release_memory_resource' declared 'static' but never defined
> > -------------------------------------------------------------------------------
> > Passed with no errors, warnings or mismatches:
> >
> > arm64-allnoconfig
> > arm-multi_v5_defconfig
> > arm-multi_v7_defconfig
> > x86_64-defconfig
> > arm-allmodconfig
> > arm-allnoconfig
> > x86_64-allnoconfig
> > arm64-defconfig
>
> Hi Greg,
>
> It seems we're down to a single warning on ARM and ARM64 now, and
> the fix just got merged as commit
>
> 842775f15090 ("xen/balloon: Fix declared-but-not-defined warning")
>
> so we can for the first time have a stable kernel that builds
> without warnings on these architectures, nice!
This is now queued up, thanks for pushing for these, it's great to see.
thanks,
greg k-h
prev parent reply other threads:[~2016-07-25 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 23:37 v4.4.14 build: 0 failures 1 warnings (v4.4.14) Build bot for Mark Brown
2016-06-25 9:23 ` Arnd Bergmann
2016-07-24 23:59 ` Greg KH [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=20160724235945.GA23085@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).