From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
xe-linux-external@cisco.com, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Maksym Kokhan <maksym.kokhan@globallogic.com>,
Daniel Walker <dwalker@fifo99.com>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org, Daniel Walker <danielwa@cisco.com>
Subject: Re: [PATCH 1/4] add generic builtin command line
Date: Tue, 16 Feb 2021 13:20:37 -0800 [thread overview]
Message-ID: <1613510437.3853.20.camel@chimera> (raw)
In-Reply-To: <20210216184247.Horde.If3nEUb5zLh4eU_4qXZCAw1@messagerie.c-s.fr>
On Tue, 2021-02-16 at 18:42 +0100, Christophe Leroy wrote:
> I'd suggest also to find the good arguments to convince us that this
> series has a real added value, not just "cisco use it in its kernels
> so it is good".
Well, IIRC, this series was endorsed by the device tree maintainers as
the preferred alternative to this:
https://lore.kernel.org/linux-devicetree/1565020400-25679-1-git-send-email-daniel@gimpelevich.san-francisco.ca.us/T/#u
The now-defunct patchwork.linux-mips.org link in that thread pointed to:
https://lore.kernel.org/linux-mips/1510796793.16864.25.camel@chimera/T/#u
When running modern kernels from ancient vendor bootloaders, it is
sometimes necessary to pick and choose bits and pieces of the info they
pass without taking it verbatim.
next prev parent reply other threads:[~2021-02-16 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 23:24 [PATCH 1/4] add generic builtin command line Daniel Walker
2019-03-20 22:53 ` Andrew Morton
2019-03-20 23:23 ` Daniel Walker
2019-03-21 3:14 ` Andrew Morton
2019-03-21 15:13 ` Daniel Walker
2019-03-21 22:15 ` Andrew Morton
2021-02-15 19:32 ` Daniel Gimpelevich
2021-02-16 17:42 ` Christophe Leroy
2021-02-16 21:20 ` Daniel Gimpelevich [this message]
2021-02-16 19:02 ` Daniel Walker
2021-02-17 21:16 ` Andrew Morton
2023-04-17 16:18 ` Tomas Mudrunka
2023-04-17 16:24 ` Daniel Walker (danielwa)
2023-10-17 10:40 ` Pratyush Brahma
2023-10-17 14:21 ` Daniel Walker (danielwa)
2023-10-19 6:43 ` Pratyush Brahma
2023-11-08 11:33 ` Christophe Leroy
2023-11-08 16:23 ` Daniel Walker (danielwa)
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=1613510437.3853.20.camel@chimera \
--to=daniel@gimpelevich.san-francisco.ca.us \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=christophe.leroy@csgroup.eu \
--cc=danielwa@cisco.com \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maksym.kokhan@globallogic.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=xe-linux-external@cisco.com \
/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).