From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Vinod Koul <vkoul@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the slave-dma tree
Date: Mon, 12 Aug 2019 19:21:47 +1000 [thread overview]
Message-ID: <20190812192147.5dd41ab7@canb.auug.org.au> (raw)
In-Reply-To: <CAK8P3a0eOyD2iTFeLC1J95WMAwyzBJJ0S5nOb+Z_y9nUy=8=qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi Arnd,
On Mon, 12 Aug 2019 11:14:08 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
>
> The warning is valid, I will send a fix.
Thanks.
> I have never seen this message though, I guess the build system just introduced
> a check for this? I don't see where this would come from in next-20190809
> (only checking with grep, not actually trying to build right now).
Yeah, we had a version of this a week or so ago and it has come back
today (I haven't done today's release yet).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-12 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 7:14 linux-next: build warning after merge of the slave-dma tree Stephen Rothwell
2019-08-12 9:14 ` Arnd Bergmann
2019-08-12 9:21 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 0:00 Stephen Rothwell
2020-02-14 4:41 ` Vinod Koul
2018-11-26 5:59 Stephen Rothwell
2018-11-26 8:09 ` Vinod Koul
2018-09-13 2:22 Stephen Rothwell
2018-09-13 7:17 ` Angelo Dureghello
2018-07-04 3:30 Stephen Rothwell
2018-07-04 4:20 ` Vinod
2018-07-05 2:47 ` Stephen Rothwell
2018-07-05 5:01 ` Vinod
2016-06-09 1:18 Stephen Rothwell
2016-06-09 6:04 ` Appana Durga Kedareswara Rao
2015-03-30 6:20 Stephen Rothwell
2015-03-30 6:26 ` Appana Durga Kedareswara Rao
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=20190812192147.5dd41ab7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vkoul@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).