From: Rob Herring <robh+dt@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH 0/3] of: base: of_parse_phandle() fixes and new variant
Date: Thu, 13 Jan 2022 20:30:07 -0600 [thread overview]
Message-ID: <CAL_Jsq+NDje8TTPWAKPKKuA6bMHEO17LFXfKJPxgbE_394bkdg@mail.gmail.com> (raw)
In-Reply-To: <3072e2f28b4f2569f5861093768398c8@walle.cc>
On Thu, Jan 13, 2022 at 6:22 AM Michael Walle <michael@walle.cc> wrote:
>
> Am 2022-01-13 09:52, schrieb Michael Walle:
> > This series is a result of the discussion in [1]. Rob suggested to
> > convert
> > the index parameter to unsigned int and drop the check for negative
> > values
> > and make them static inline.
>
> Oh I haven't thought this through.. If this is going via another tree
> than
> the nvmem patches, then I'd need either wait one kernel release, or
> there
> need to be an immutable tag, right?
I can pick this up for 5.17-rc1 if we can get it sorted soon.
Rob
prev parent reply other threads:[~2022-01-14 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 8:52 [PATCH 0/3] of: base: of_parse_phandle() fixes and new variant Michael Walle
2022-01-13 8:52 ` [PATCH 1/3] of: base: convert index to unsigned for of_parse_phandle() Michael Walle
2022-01-14 2:29 ` Rob Herring
2022-01-13 8:52 ` [PATCH 2/3] of: property: use unsigned index for of_link_property() Michael Walle
2022-01-13 8:52 ` [PATCH 3/3] of: base: add of_parse_phandle_with_optional_args() Michael Walle
2022-01-13 12:22 ` [PATCH 0/3] of: base: of_parse_phandle() fixes and new variant Michael Walle
2022-01-14 2:30 ` Rob Herring [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=CAL_Jsq+NDje8TTPWAKPKKuA6bMHEO17LFXfKJPxgbE_394bkdg@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
/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).