From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ladislav Michl <ladis@linux-mips.org>,
Michael Trensch <MTrensch@hilscher.com>,
nagasureshkumarrelli@gmail.com,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Olof Johansson <olof@lixom.net>,
Robert Schwebel <r.schwebel@pengutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Re: Hilscher NetX mach-netx refactorings
Date: Tue, 15 Jan 2019 11:14:41 +0100 [thread overview]
Message-ID: <CAK8P3a2c+W7rZu1T2U1ryZZgaOAs6nqcp4h3m9fTQtZ4UR3+kQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYnbCmfTVB_aFX-vhkbWma=60U0D6pKZ8bcKdxCdSXdyA@mail.gmail.com>
On Mon, Jan 14, 2019 at 3:22 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Mon, Jan 14, 2019 at 12:26 PM Michael Trensch <MTrensch@hilscher.com> wrote:
> > The netX4000 platform is only built using a device tree. The device tree
> > files were sometime ago moved out of the kernel into our yocto layer to
> > reduce maintenance and have a single location. I know this conflicts
> > with mainlining.
>
> No big deal where you keep the files as long as they are merged
> when we implement the platform in the upstream kernel.
Agreed. It's usually best to have all reference boards working out of the
box using the dts files supplied with the kernel, but for customer specific
machines, we don't care much whether they are shipped with kernel
or some other way (e.g. bootloader, formware or distro).
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-15 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 8:35 Hilscher NetX mach-netx refactorings Linus Walleij
2019-01-12 12:03 ` Arnd Bergmann
2019-01-13 12:14 ` Linus Walleij
2019-01-13 15:50 ` Ladislav Michl
2019-01-13 22:39 ` Linus Walleij
2019-01-14 11:26 ` Michael Trensch
2019-01-14 14:22 ` Linus Walleij
2019-01-15 7:05 ` Michael Trensch
2019-01-15 10:11 ` Arnd Bergmann
2019-01-15 10:14 ` Arnd Bergmann [this message]
2019-01-14 10:35 ` Sascha Hauer
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=CAK8P3a2c+W7rZu1T2U1ryZZgaOAs6nqcp4h3m9fTQtZ4UR3+kQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=MTrensch@hilscher.com \
--cc=kernel@pengutronix.de \
--cc=ladis@linux-mips.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nagasureshkumarrelli@gmail.com \
--cc=olof@lixom.net \
--cc=r.schwebel@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).