From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Jiri Slaby" <jslaby@suse.com>,
linux-serial@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Prabhakar Mahadev Lad" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] serial: 8250_em: Fix UART port type
Date: Mon, 20 Mar 2023 14:33:10 +0100 [thread overview]
Message-ID: <ZBhglhuXBlSPVRVx@kroah.com> (raw)
In-Reply-To: <20230320122225.414976-1-biju.das.jz@bp.renesas.com>
On Mon, Mar 20, 2023 at 12:22:25PM +0000, Biju Das wrote:
> commit 32e293be736b853f168cd065d9cbc1b0c69f545d upstream.
>
> As per HW manual for EMEV2 "R19UH0040EJ0400 Rev.4.00", the UART
> IP found on EMMA mobile SoC is Register-compatible with the
> general-purpose 16750 UART chip. Fix UART port type as 16750 and
> enable 64-bytes fifo support.
>
> Fixes: 22886ee96895 ("serial8250-em: Emma Mobile UART driver V2")
> Cc: stable@vger.kernel.org # 4.19.y
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> Link: https://lore.kernel.org/r/20230227114152.22265-2-biju.das.jz@bp.renesas.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [biju: manually fixed the conflicts]
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> Resending to 4.19 with confilcts [1] fixed.
> [1] https://lore.kernel.org/stable/1679303539169236@kroah.com/
Both now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-03-20 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 12:22 [PATCH] serial: 8250_em: Fix UART port type Biju Das
2023-03-20 13:33 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 13:12 Biju Das
2023-03-20 12:04 Biju Das
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=ZBhglhuXBlSPVRVx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=jslaby@suse.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).