From: santosh.shilimkar@oracle.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM: dts: keystone*: Continued warnings cleanups
Date: Thu, 4 Jan 2018 11:10:22 -0800 [thread overview]
Message-ID: <03ab6d33-1576-e405-3eb3-96572f7da80b@oracle.com> (raw)
In-Reply-To: <20180102170202.15045-1-afd@ti.com>
On 1/2/2018 9:01 AM, Andrew F. Davis wrote:
> Hello all,
>
> Just a couple cleanups for DT warnings when compiling with W=1.
>
> This clears up 51 more warnings when building keystone_defconfig.
>
> Based on Santosh's "for_4.16/keystone-dts" branch.
>
Will see if this can be queued up post merge window as 'non-critical'
fixes o.w it waits for 4.17. Please repost it after addressing
Suman's comments.
Regards,
Santosh
prev parent reply other threads:[~2018-01-04 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180102170202.15045-1-afd@ti.com>
[not found] ` <20180102170202.15045-2-afd@ti.com>
2018-01-02 23:30 ` [PATCH 1/8] ARM: dts: keystone: Move keystone_irq to under device-state-control Suman Anna
2018-01-04 19:34 ` Andrew F. Davis
2018-01-04 19:10 ` Santosh Shilimkar [this message]
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=03ab6d33-1576-e405-3eb3-96572f7da80b@oracle.com \
--to=santosh.shilimkar@oracle.com \
--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