From: Olof Johansson <olof@lixom.net>
To: Alistair Francis <alistair@alistair23.me>
Cc: Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alistair23@gmail.com
Subject: Re: [PATCH 2/2] remarkable2_defconfig: Add initial support for the reMarkable2
Date: Sun, 17 Jan 2021 17:29:58 -0800 [thread overview]
Message-ID: <CAOesGMiLZGdjQTLj48B8dXV1vv2p-NG751m-bh61mJ-10N-rAw@mail.gmail.com> (raw)
In-Reply-To: <20210117035140.1437-2-alistair@alistair23.me>
Hi Alistair,
On Sun, Jan 17, 2021 at 3:09 PM Alistair Francis <alistair@alistair23.me> wrote:
>
> This defconfig is based on the one released by reMarkable with their
> 4.14 kernel. I have updated it to match the latest kernels.
>
> Signed-off-by: Alistair Francis <alistair@alistair23.me>
It's awesome to see upstream support for contemporary consumer
products being posted, thanks!
When it comes to a dedicated defconfig, is that necessary in this
case? The needed drivers should be possible to enable either in
imx_v6_v7_defconfig, or in multi_v7_defconfig (or, rather, both)?
Adding new defconfigs is something we're avoiding as much as possible,
since it adds CI overhead, and defconfigs easily get churny due to
options moving around.
In some cases we do it once per SoC family (i.e. the i.MX defconfigs),
but we avoid it for products.
-Olof
next prev parent reply other threads:[~2021-01-18 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 3:51 [PATCH 1/2] imx7d-remarkable2.dts: Initial device tree for reMarkable2 Alistair Francis
2021-01-17 3:51 ` [PATCH 2/2] remarkable2_defconfig: Add initial support for the reMarkable2 Alistair Francis
2021-01-18 1:29 ` Olof Johansson [this message]
2021-01-18 1:36 ` Alistair Francis
2021-01-18 2:03 ` Olof Johansson
2021-01-19 5:42 ` Alistair Francis
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=CAOesGMiLZGdjQTLj48B8dXV1vv2p-NG751m-bh61mJ-10N-rAw@mail.gmail.com \
--to=olof@lixom.net \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).