From: Ilya Lipnitskiy <ilya.lipnitskiy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
Jon Loeliger <loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Ilya Lipnitskiy
<ilya.lipnitskiy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/4] checks: clean up string parsing
Date: Mon, 3 May 2021 20:59:40 -0700 [thread overview]
Message-ID: <20210504035944.8453-1-ilya.lipnitskiy@gmail.com> (raw)
Add a new function, strends(), as suggested in [0]. Replace existing
suffix logic with calls to strends().
Make nr-gpios exception stricter by aligning with the devicetree spec
and the logic in the Linux kernel.
Add a test case to cover correct non-deprecated GPIO properties.
[0]: https://www.spinics.net/lists/devicetree-compiler/msg03634.html
Ilya Lipnitskiy (4):
checks: tigthen up nr-gpios prop exception
dtc.h: add strends for suffix matching
checks: replace strstr and strrchr with strends
tests: add a positive gpio test case
checks.c | 25 +++++++------------------
dtc.h | 10 ++++++++++
tests/good-gpio.dts | 12 ++++++++++++
tests/run_tests.sh | 2 ++
4 files changed, 31 insertions(+), 18 deletions(-)
create mode 100644 tests/good-gpio.dts
--
2.31.1
next reply other threads:[~2021-05-04 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 3:59 Ilya Lipnitskiy [this message]
[not found] ` <20210504035944.8453-1-ilya.lipnitskiy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-05-04 3:59 ` [PATCH 1/4] checks: tigthen up nr-gpios prop exception Ilya Lipnitskiy
2021-05-04 3:59 ` [PATCH 2/4] dtc.h: add strends for suffix matching Ilya Lipnitskiy
2021-05-04 3:59 ` [PATCH 3/4] checks: replace strstr and strrchr with strends Ilya Lipnitskiy
2021-05-04 3:59 ` [PATCH 4/4] tests: add a positive gpio test case Ilya Lipnitskiy
2021-05-04 4:53 ` [PATCH 0/4] checks: clean up string parsing David Gibson
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=20210504035944.8453-1-ilya.lipnitskiy@gmail.com \
--to=ilya.lipnitskiy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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).