From: Shawn Guo <shawnguo@kernel.org>
To: 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>,
Tim Harvey <tharvey@gateworks.com>
Subject: Re: linux-next: build warnings after merge of the imx-mxs tree
Date: Wed, 24 Jun 2020 09:35:06 +0800 [thread overview]
Message-ID: <20200624011800.GA31961@dragon> (raw)
In-Reply-To: <20200624095007.141f0357@canb.auug.org.au>
On Wed, Jun 24, 2020 at 09:50:07AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
...
> Introduced by commits
>
> 26d7c769d460 ("ARM: dts: imx6qdl-gw53xx: allow boot firmware to set eth1 MAC")
> 48d799918adf ("ARM: dts: imx6qdl-gw54xx: allow boot firmware to set eth1 MAC")
Sorry, Stephen. I have just taken them out.
Shawn
next prev parent reply other threads:[~2020-06-24 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 23:50 linux-next: build warnings after merge of the imx-mxs tree Stephen Rothwell
2020-06-24 1:35 ` Shawn Guo [this message]
2020-06-24 15:15 ` Tim Harvey
-- strict thread matches above, loose matches on Subject: below --
2021-12-16 23:53 Stephen Rothwell
2021-12-17 3:07 ` Shawn Guo
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=20200624011800.GA31961@dragon \
--to=shawnguo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tharvey@gateworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.