From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Stephen Boyd <swboyd@chromium.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] tty: serial: sh-sci: Fix transmit end interrupt handler
Date: Fri, 17 Mar 2023 10:07:27 +0100 [thread overview]
Message-ID: <ZBQtzwCDDbIYM+yv@shikoro> (raw)
In-Reply-To: <TYCPR01MB5933865E5D673865B7C4A85586BD9@TYCPR01MB5933.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi Biju,
> Wolfram, Can you please confirm transmit end interrupt handler worked for you
> with the commit 4c84c1b3acca ("ARM: shmobile: r7s72100: add scif nodes to dtsi")
That was nearly 10 years ago :) I can't recall if a specific interrupt
worked. But SCIF worked. So, if it was needed for proper operation, then
it probably worked. If it was not needed, no idea.
This is all for a Fixes: tag, or? Is it that important?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-17 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 16:01 [PATCH] tty: serial: sh-sci: Fix transmit end interrupt handler Biju Das
2023-03-16 16:13 ` Geert Uytterhoeven
2023-03-16 16:34 ` Biju Das
2023-03-16 17:54 ` Geert Uytterhoeven
2023-03-17 7:59 ` Biju Das
2023-03-17 8:05 ` Geert Uytterhoeven
2023-03-17 8:08 ` Biju Das
2023-03-17 9:00 ` Biju Das
2023-03-17 9:05 ` Geert Uytterhoeven
2023-03-17 9:07 ` Wolfram Sang [this message]
2023-03-17 9:16 ` Wolfram Sang
2023-03-17 9:21 ` Biju Das
2023-03-17 9:04 ` Geert Uytterhoeven
2023-03-17 9:15 ` Biju Das
2023-03-17 9:38 ` Geert Uytterhoeven
2023-03-17 13:47 ` Biju Das
2023-03-17 14:30 ` Geert Uytterhoeven
2023-03-17 14:40 ` Biju Das
-- strict thread matches above, loose matches on Subject: below --
2023-04-11 10:08 Biju Das
2023-04-11 14:14 ` Greg Kroah-Hartman
2023-04-11 14:24 ` Biju Das
2023-04-11 14:40 ` Biju Das
2023-04-11 14:56 ` Greg Kroah-Hartman
2023-04-11 15:36 ` Biju Das
2023-04-12 6:37 ` Greg Kroah-Hartman
2023-04-12 6:52 ` 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=ZBQtzwCDDbIYM+yv@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=swboyd@chromium.org \
--cc=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox