From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Yunus Bas <y.bas@phytec.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the imx-mxs tree
Date: Fri, 17 Dec 2021 11:07:15 +0800 [thread overview]
Message-ID: <20211217030714.GN4216@dragon> (raw)
In-Reply-To: <20211217105338.315a26b3@canb.auug.org.au>
On Fri, Dec 17, 2021 at 10:53:38AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
Fixed. Thanks for the reporting!
Shawn
next prev parent reply other threads:[~2021-12-17 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 23:53 linux-next: build warnings after merge of the imx-mxs tree Stephen Rothwell
2021-12-17 3:07 ` Shawn Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-23 23:50 Stephen Rothwell
2020-06-24 1:35 ` Shawn Guo
2020-06-24 15:15 ` Tim Harvey
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=20211217030714.GN4216@dragon \
--to=shawnguo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=y.bas@phytec.de \
/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.