From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
<gregkh@linuxfoundation.org>, <jirislaby@kernel.org>
Cc: <linux-serial@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] tty: serial: samsung: add dedicated compatible for exynosauto SoCs
Date: Mon, 27 Apr 2026 15:56:09 +0530 [thread overview]
Message-ID: <33b901dcd630$4587bc50$d09734f0$@samsung.com> (raw)
In-Reply-To: <8998d2ae-cb6e-458d-8551-6b44f81b1c60@kernel.org>
Hi Krzysztof,
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Monday, April 27, 2026 12:10 PM
> To: Alim Akhtar <alim.akhtar@samsung.com>; gregkh@linuxfoundation.org;
> jirislaby@kernel.org
> Cc: linux-serial@vger.kernel.org; linux-samsung-soc@vger.kernel.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH] tty: serial: samsung: add dedicated compatible for
> exynosauto SoCs
> >
.
.
.
> >> Entire reasoning for doing this patch is wrong. And patch itself is
> >> NOOP (at least by quick look).
> > Thanks for a quick review, Can you please check the part of the patch
> > which adds OF_EARLYCON_DECLARE to add earlycon support?
> >
>
> It also feels unnecessary - existing compatible will be used for earlycon, no?
> If matching by existing compatible does not work, commit msg should explain
> that.
>
Yes, it fall back to exynos850 and earlycon does work with fallback compatible, Thanks!
> Best regards,
> Krzysztof
prev parent reply other threads:[~2026-04-27 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260424100201epcas5p371dd69955076938ee41ed0d823433056@epcas5p3.samsung.com>
2026-04-24 10:18 ` [PATCH] tty: serial: samsung: add dedicated compatible for exynosauto SoCs Alim Akhtar
2026-04-24 16:12 ` Krzysztof Kozlowski
2026-04-26 17:18 ` Alim Akhtar
2026-04-27 6:40 ` Krzysztof Kozlowski
2026-04-27 10:26 ` Alim Akhtar [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='33b901dcd630$4587bc50$d09734f0$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.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