From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: jcmvbkbc@gmail.com, rdunlap@infradead.org,
ilpo.jarvinen@linux.intel.com, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
jirislaby@kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/tty/serial: move ESP32 UART drivers into staging
Date: Sun, 8 Mar 2026 15:16:14 +0100 [thread overview]
Message-ID: <2026030845-chastise-briskness-3317@gregkh> (raw)
In-Reply-To: <20260308131412.1102749-1-julianbraha@gmail.com>
On Sun, Mar 08, 2026 at 01:14:12PM +0000, Julian Braha wrote:
> These drivers were added about 3 years ago, and depend on the
> XTENSA_PLATFORM_ESP32 config option which has never existed,
> so no device can actually use them.
> They can only be compiled with COMPILE_TEST.
>
> As you can see, this config option is still undefined
> in the downstream tree:
> https://github.com/search?q=repo%3Ajcmvbkbc%2Flinux-xtensa%20XTENSA_PLATFORM_ESP32&type=code
>
> I propose moving these drivers into staging
> until there is a device that can boot the mainline kernel and use them.
Why not just delete them? What can staging do to help out here? If
these can't be built, or used, don't drop them in staging, that's not
what that part of the kernel is for, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-08 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 13:14 [PATCH] drivers/tty/serial: move ESP32 UART drivers into staging Julian Braha
2026-03-08 14:16 ` Greg KH [this message]
2026-03-09 7:44 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2026-03-08 13:11 Julian Braha
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=2026030845-chastise-briskness-3317@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jcmvbkbc@gmail.com \
--cc=jirislaby@kernel.org \
--cc=julianbraha@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@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