From: Stephen Boyd <sboyd@kernel.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wen He <wen.he_1@nxp.com>
Subject: Re: linux-next: build warnings after merge of the clk tree
Date: Sun, 02 Feb 2020 21:25:27 -0800 [thread overview]
Message-ID: <20200203052527.B3B1820721@mail.kernel.org> (raw)
In-Reply-To: <20200203091633.3265a3f1@canb.auug.org.au>
Quoting Stephen Rothwell (2020-02-02 14:16:33)
> Hi all,
>
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
Thanks. I missed this and I've sent a fix now.
next prev parent reply other threads:[~2020-02-03 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 22:16 linux-next: build warnings after merge of the clk tree Stephen Rothwell
2020-02-03 5:25 ` Stephen Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-20 23:34 Stephen Rothwell
2017-06-21 15:15 ` Anup Patel
2017-06-21 16:13 ` Stephen Boyd
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=20200203052527.B3B1820721@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sfr@canb.auug.org.au \
--cc=wen.he_1@nxp.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).