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" <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"
<linux-renesas-soc@vger.kernel.org>, stable <stable@kernel.org>
Subject: Re: [PATCH] tty: serial: sh-sci: Fix transmit end interrupt handler
Date: Tue, 11 Apr 2023 16:56:41 +0200 [thread overview]
Message-ID: <2023041158-crisped-obtrusive-2309@gregkh> (raw)
In-Reply-To: <OS0PR01MB59220D9E0C52F5413046CAFB869A9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On Tue, Apr 11, 2023 at 02:40:52PM +0000, Biju Das wrote:
> Hi Greg,
>
> > Subject: RE: [PATCH] tty: serial: sh-sci: Fix transmit end interrupt handler
> >
> > Hi Greg,
> >
> > Thanks for the feedback.
> >
> > > Subject: Re: [PATCH] tty: serial: sh-sci: Fix transmit end interrupt
> > > handler
> > >
> > > On Tue, Apr 11, 2023 at 11:08:59AM +0100, Biju Das wrote:
> > > > commit b43a18647f03c87e77d50d6fe74904b61b96323e upstream.
> > > >
> > > > The fourth interrupt on SCI port is transmit end interrupt compared
> > > > to the break interrupt on other port types. So, shuffle the
> > > > interrupts to fix the transmit end interrupt handler.
> > > >
> > > > Fixes: e1d0be616186 ("sh-sci: Add h8300 SCI")
> > > > Cc: stable <stable@kernel.org>
> > > > Suggested-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > > Link:
> > > > 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.14 with confilcts [1] fixed.
> > > > [1]
> > >
> > > You did not actually build your patch, as it breaks the build :(
> >
> > Actually, I build the patch, but did not test it on target as I don't have
> > the platform to test it.
> >
> > I got some issues while building modules which is unrelated to this change.
> >
> > Anyway, I will double check again and confirm.
>
> I confirm, there is an issue with this patch.
>
> I disabled building modules from my build script and it showed the below error.
> So I would like to drop this patch for 4.14 as this header file does not exist for 4.14.
>
> drivers/tty/serial/sh-sci.c:40:10: fatal error: linux/minmax.h: No such file or directory
> 40 | #include <linux/minmax.h>
> | ^~~~~~~~~~~~~~~~
Yes, minmax is not there, but the function needed by that is there
(hint, I had to remove that include in 4.19). Remove it and see the
next error you get :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-11 14:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 10:08 [PATCH] tty: serial: sh-sci: Fix transmit end interrupt handler 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 [this message]
2023-04-11 15:36 ` Biju Das
2023-04-12 6:37 ` Greg Kroah-Hartman
2023-04-12 6:52 ` Biju Das
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 16:01 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
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
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=2023041158-crisped-obtrusive-2309@gregkh \
--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@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