From: Joel Stanley <joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: [PATCH v3 0/2] dtc: Improve checks for i2c reg properties
Date: Thu, 28 May 2020 18:26:48 +0930 [thread overview]
Message-ID: <20200528085650.1417942-1-joel@jms.id.au> (raw)
This is to fix a build warning in the Linux kernel caused by dtc
incorrectly warning about I2C_OWN_SLAVE_ADDRESS.
v3 fixes the 10 bit size check
v2 contains a second patch to check for 10 bit vs 7 bit addresses.
Joel Stanley (2):
checks: Remove warning for I2C_OWN_SLAVE_ADDRESS
checks: Improve i2c reg property checking
checks.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-28 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:56 Joel Stanley [this message]
2020-05-28 8:56 ` [PATCH v3 1/2] checks: Remove warning for I2C_OWN_SLAVE_ADDRESS Joel Stanley
[not found] ` <20200528085650.1417942-1-joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org>
2020-05-28 8:56 ` [PATCH v3 2/2] checks: Improve i2c reg property checking Joel Stanley
[not found] ` <20200528085650.1417942-3-joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org>
2020-06-02 8:01 ` Serge Semin
2020-06-02 8:28 ` Andy Shevchenko
[not found] ` <CAHp75VdkBbDhFSYQYxuej=XH1MYAq-p6AWZZRLpW_iKt9D31_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-06-04 7:14 ` David Gibson
2020-05-29 22:33 ` [PATCH v3 0/2] dtc: Improve checks for i2c reg properties Rob Herring
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=20200528085650.1417942-1-joel@jms.id.au \
--to=joel-u3u1mxzcp9khxe+lvdladg@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).