From: Michael Walle <michael@walle.cc>
To: Rob Herring <robh+dt@kernel.org>
Cc: Robert Marko <robimarko@gmail.com>,
Frank Rowand <frowand.list@gmail.com>,
Peng Fan <peng.fan@nxp.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
devicetree@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, Aisheng Dong <aisheng.dong@nxp.com>
Subject: Re: [PATCH] of: property: fix #nvmem-cell-cells parsing
Date: Fri, 13 Jan 2023 11:20:34 +0100 [thread overview]
Message-ID: <729fb97c96216168f73d1a7f01bfd70d@walle.cc> (raw)
In-Reply-To: <CAL_JsqLN0jd0nT7rC7SBMh2zLsAvGCafknnS_oqJJj+=c1m9pg@mail.gmail.com>
>> > Commit 67b8497f005f ("of: property: make #.*-cells optional for simple
>> > props") claims to make the cells-name property optional for simple
>> > properties, but changed the code for the wrong property, i.e. for
>> > DEFINE_SUFFIX_PROP(). Fix that.
>> >
>> > Fixes: 67b8497f005f ("of: property: make #.*-cells optional for simple props")
>> > Reported-by: Peng Fan <peng.fan@nxp.com>
>> > Signed-off-by: Michael Walle <michael@walle.cc>
>> > Tested-by: Robert Marko <robimarko@gmail.com>
>> > ---
>> > drivers/of/property.c | 8 ++++----
>> > 1 file changed, 4 insertions(+), 4 deletions(-)
>> >
>>
>> Applied, thanks!
>
> Or not. 67b8497f005f is not in my tree, so
>
> Acked-by: Rob Herring <robh@kernel.org>
Thanks! Srinivas, can you pick it up to get rid of the errors/warnings
in linux-next?
-michael
next prev parent reply other threads:[~2023-01-13 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 23:30 [PATCH] of: property: fix #nvmem-cell-cells parsing Michael Walle
2023-01-11 2:45 ` Peng Fan
2023-01-13 1:32 ` Rob Herring
2023-01-13 1:33 ` Rob Herring
2023-01-13 10:20 ` Michael Walle [this message]
2023-01-20 17:48 ` Srinivas Kandagatla
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=729fb97c96216168f73d1a7f01bfd70d@walle.cc \
--to=michael@walle.cc \
--cc=aisheng.dong@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--cc=srinivas.kandagatla@linaro.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 NNTP newsgroup(s).