From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robh@kernel.org>
Cc: "Saravana Kannan" <saravanak@google.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] fdtoverlay: Remove bogus type info from help text
Date: Thu, 30 May 2024 15:31:55 +0200 [thread overview]
Message-ID: <CAMuHMdWxxDu-V_drs+dMdycQHY_+v0sPH7bVO_2-ixGWQkdTjg@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLL3g4+nfu2NmC0drR-m5u287EBvK9jbY43XC=bSSVSpQ@mail.gmail.com>
Hi Rob,
On Thu, May 30, 2024 at 2:31 PM Rob Herring <robh@kernel.org> wrote:
> On Wed, May 29, 2024 at 5:11 AM Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> >
> > "fdtoverlay -h" shows a.o.:
> >
> > <type> s=string, i=int, u=unsigned, x=hex
> > Optional modifier prefix:
> > hh or b=byte, h=2 byte, l=4 byte (default)
> >
> > However, unlike fdtget and fdtput, fdtoverlay does not support the
> > "-t"/"--type" option.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> > Upstream dtc has Uwe's commit 2cdf93a6d402a161 ("fdtoverlay: Fix usage
> > string to not mention "<type>"").
>
> So you want me to sync upstream? That's how upstream commits get into
> the kernel. I don't take patches (unless there's some urgent
> breakage).
If that's the policy, then yes please ;-)
Apparently it's been +2.5y since last sync...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-05-30 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 10:11 [PATCH v2] fdtoverlay: Remove bogus type info from help text Geert Uytterhoeven
2024-05-30 12:31 ` Rob Herring
2024-05-30 13:31 ` Geert Uytterhoeven [this message]
2024-05-31 13:42 ` Rob Herring
2024-05-31 14:06 ` Geert Uytterhoeven
2024-05-31 14:38 ` Rob Herring
2024-05-31 15:00 ` 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=CAMuHMdWxxDu-V_drs+dMdycQHY_+v0sPH7bVO_2-ixGWQkdTjg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).