From: David Sterba <dsterba@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
David Daney <david.daney@cavium.com>,
Carlos Munoz <cmunoz@caviumnetworks.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@linaro.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: next/master build: 214 builds: 29 failed, 185 passed, 29 errors, 68 warnings (next-20171016)
Date: Tue, 17 Oct 2017 15:12:20 +0200 [thread overview]
Message-ID: <20171017131220.GX3521@suse.cz> (raw)
In-Reply-To: <CAK8P3a1Qk+H3zp23zR=3Wsh-Yp3YOZ0bF6BNcFHjnEHd9XnCjA@mail.gmail.com>
On Tue, Oct 17, 2017 at 11:00:04AM +0200, Arnd Bergmann wrote:
> > 2 fs/btrfs/tree-checker.c:186:4: warning: format '%lu' expects argument of type 'long unsigned int', but argument 6 has type 'unsigned int' [-Wformat=]
> > 1 fs/btrfs/tree-checker.c:186:70: warning: format '%lu' expects argument of type 'long unsigned int', but argument 6 has type 'unsigned int' [-Wformat=]
>
> I sent a patch a few days ago, Dave Sterba reviewed it, but it hasn't
> gone in yet.
The patch was picked last Friday, and is now part of linux-next tree
https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git/commit/?h=for-next&id=6881041b521fff47c3b31269ec9b8b5ebe7d631e
There might be a few days delay, caused by testing, before my kernel.org
for-next branch is updated and then picked by linux-next.
prev parent reply other threads:[~2017-10-17 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59e53a9c.0a98df0a.acf5c.fc96@mx.google.com>
2017-10-17 9:00 ` next/master build: 214 builds: 29 failed, 185 passed, 29 errors, 68 warnings (next-20171016) Arnd Bergmann
2017-10-17 13:12 ` David Sterba [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=20171017131220.GX3521@suse.cz \
--to=dsterba@suse.cz \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=broonie@linaro.org \
--cc=cmunoz@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=jpoimboe@redhat.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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).