From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bhavya Kapoor <b-kapoor@ti.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: "Udit Kumar" <u-kumar1@ti.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Biju Das" <biju.das.jz@bp.renesas.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Will Deacon" <will@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>
Subject: Re: [PATCH] arm64: defconfig: Modify number of usable 8250 uart ports
Date: Tue, 28 May 2024 08:34:18 +0200 [thread overview]
Message-ID: <ac2f4ba0-e48a-480e-98da-500041f564ac@linaro.org> (raw)
In-Reply-To: <9170a555-7cd3-4888-bad3-01b71c6f445e@ti.com>
On 28/05/2024 08:26, Bhavya Kapoor wrote:
> Hi Arnd, our most boards have 6 uarts that can be used in the runtime
>
> but overall our SoC has 12 uarts. And some of our customers have this
>
> requirements that on their custom boards they use more than 8 uarts on their
>
> boards. Thus, we need to enable this to 12 uarts.
defconfig is for boards in tree, for developers, not for customers.
Argument that some out-of-tree user has more uarts does not mean much
for defconfig. If they have some weird hardware, shall we enable it? Or
if they want DEBUG_KOBJECT? Or anything else?
You mistake kernel development defconfig with a distro or product config.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-05-28 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 9:57 Bhavya Kapoor
2024-05-16 10:07 ` Bhavya Kapoor
2024-05-17 6:49 ` Arnd Bergmann
2024-05-28 6:26 ` Bhavya Kapoor
2024-05-28 6:34 ` Krzysztof Kozlowski [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=ac2f4ba0-e48a-480e-98da-500041f564ac@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=b-kapoor@ti.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=quic_bjorande@quicinc.com \
--cc=shawnguo@kernel.org \
--cc=u-kumar1@ti.com \
--cc=will@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
all inboxes | Powered by JetHome®