From: "Faraz Ata" <faraz.ata@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
<alim.akhtar@samsung.com>, <gregkh@linuxfoundation.org>,
<jirislaby@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
<dev.tailor@samsung.com>, <rosa.pila@samsung.com>
Subject: RE: [PATCH v3] tty: serial: samsung_tty: support 18 uart ports
Date: Thu, 17 Apr 2025 11:02:24 +0530 [thread overview]
Message-ID: <06cb01dbaf5a$1ea1a8b0$5be4fa10$@samsung.com> (raw)
In-Reply-To: <d350841c-3560-4511-a866-9490737e48f7@kernel.org>
Hello Krzysztof
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Thursday, April 17, 2025 10:50 AM
> To: Faraz Ata <faraz.ata@samsung.com>; alim.akhtar@samsung.com;
> gregkh@linuxfoundation.org; jirislaby@kernel.org
> Cc: linux-arm-kernel@lists.infradead.org; linux-samsung-
> soc@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> serial@vger.kernel.org; dev.tailor@samsung.com; rosa.pila@samsung.com
> Subject: Re: [PATCH v3] tty: serial: samsung_tty: support 18 uart ports
>
> On 17/04/2025 06:34, Faraz Ata wrote:
> > ExynosAutov920 SoC supports 18 UART ports, update the value of
> UART_NR
> > to accommodate the same.
> >
> > Signed-off-by: Faraz Ata <faraz.ata@samsung.com>
> > ---
> > Changes in v3:
> > - Fixed review comments from Krzysztof
>
> Which ones? What changed?
>
While sending v2 change log was missed unintentionally.
Added missed change log in v3.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-04-17 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250417042427epcas5p2df3d35803adcb24da7d83e5df586380d@epcas5p2.samsung.com>
2025-04-17 4:34 ` [PATCH v3] tty: serial: samsung_tty: support 18 uart ports Faraz Ata
2025-04-17 5:19 ` Krzysztof Kozlowski
2025-04-17 5:32 ` Faraz Ata [this message]
2025-04-25 11:39 ` Greg KH
2025-04-28 12:14 ` Faraz Ata
2025-04-28 17:10 ` 'Greg KH'
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='06cb01dbaf5a$1ea1a8b0$5be4fa10$@samsung.com' \
--to=faraz.ata@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=dev.tailor@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rosa.pila@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.