From: Wolfram Sang <wsa@the-dreams.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof's autobuilder <build@lixom.net>,
Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Joe Carnuccio <joe.carnuccio@cavium.com>,
Himanshu Madhani <himanshu.madhani@cavium.com>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, qla2xxx-upstream@qlogic.com,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: next build: 113 warnings 0 failures (next/next-20170605)
Date: Wed, 7 Jun 2017 00:36:22 +0200 [thread overview]
Message-ID: <20170606223621.GA3628@katana> (raw)
In-Reply-To: <CAK8P3a1D0r9XAfGN95EkiaXvCmkJq1Em=xggJw87yX7YH7o-vA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
> > 2 drivers/i2c/i2c-stub.c:18:0: warning: "DEBUG" redefined
>
> Caused by 6c42778780c4 ("i2c: stub: use pr_fmt"): "#define DEBUG"
> now conflicts with "ccflags-$(CONFIG_I2C_DEBUG_CORE) := -DDEBUG"
> in the Makefile.
I'll fix it tomorrow!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-06 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59351e18.c490630a.4dca5.e785@mx.google.com>
2017-06-06 13:14 ` next build: 113 warnings 0 failures (next/next-20170605) Arnd Bergmann
2017-06-06 22:36 ` Wolfram Sang [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=20170606223621.GA3628@katana \
--to=wsa@the-dreams.de \
--cc=Bart.VanAssche@sandisk.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=himanshu.madhani@cavium.com \
--cc=jdelvare@suse.de \
--cc=joe.carnuccio@cavium.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=olof@lixom.net \
--cc=qla2xxx-upstream@qlogic.com \
--cc=wsa+renesas@sang-engineering.com \
/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).