From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/6] i.MX device tree updates for 4.17
Date: Fri, 16 Mar 2018 09:30:29 +0800 [thread overview]
Message-ID: <20180316013028.GP26859@dragon> (raw)
In-Reply-To: <CAOMZO5DK8+5rYrMbCk9v1maYNcinAiTk0G-=wUD1CR6JLga_KA@mail.gmail.com>
On Thu, Mar 15, 2018 at 03:12:03PM -0300, Fabio Estevam wrote:
> On Thu, Mar 15, 2018 at 2:22 PM, Fabio Estevam <festevam@gmail.com> wrote:
>
> > My DTC warning patches were generated against Shaw's tree, which is
> > based on 4.16-rc1.
> >
> > In his trees these warnings do not appear, so I haven't fixed them yet.
> >
> > I can send more patches to fix the remaining i.MX DTC warnings against
> > linux-next, but that will probably be for 4.18.
>
> Just tried linux-next and I see that these warnings happen even
> without building with W=1.
That should be because DTC gets upgraded to 1.4.6 on linux-next from
version 1.4.5 on 4.16-rc.
> I will send some patches to fix them.
I received the patches and will send them to Arnd in another pull
request.
Shawn
next prev parent reply other threads:[~2018-03-16 1:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 11:36 [GIT PULL 1/6] i.MX drivers updates for 4.17 Shawn Guo
2018-03-15 11:36 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2018-03-15 15:12 ` Arnd Bergmann
2018-03-16 0:55 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 3/6] i.MX device tree updates with new clock " Shawn Guo
2018-03-15 15:03 ` Arnd Bergmann
2018-03-15 11:36 ` [GIT PULL 4/6] i.MX device tree updates " Shawn Guo
2018-03-15 15:08 ` Arnd Bergmann
2018-03-15 16:58 ` Arnd Bergmann
2018-03-15 17:22 ` Fabio Estevam
2018-03-15 18:12 ` Fabio Estevam
2018-03-16 1:30 ` Shawn Guo [this message]
2018-03-15 11:36 ` [GIT PULL 5/6] Freescale arm64 " Shawn Guo
2018-03-15 15:29 ` Arnd Bergmann
2018-03-16 1:56 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 6/6] i.MX defconfig " Shawn Guo
2018-03-15 15:21 ` Arnd Bergmann
2018-03-15 22:48 ` Fabio Estevam
2018-03-15 23:06 ` Fabio Estevam
2018-03-26 11:42 ` [GIT PULL v2 " Shawn Guo
2018-03-27 13:11 ` Arnd Bergmann
2018-03-15 15:25 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
2018-03-16 0:47 ` Shawn Guo
2018-03-16 1:22 ` Anson Huang
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=20180316013028.GP26859@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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