On Tue, 19 Apr 2022, Greg Kroah-Hartman wrote:
> On Tue, Apr 19, 2022 at 11:09:56AM +0300, Ilpo Järvinen wrote:
> > Hi Greg,
> >
> > This change now appears in your tty-next tree.
>
> What change? Please never top-post.
f6f586102add59d57bcc6eea06fdeaae11bb17a1 (serial: 8250: Handle UART
without interrupt on TEMT using em485).
> > As you seem to have missed
> > there is an obvious problem with it, I'm asking which direction I should
> > take to fix it.
>
> Send a fix! You don't need my permission to do so.
Yes, I know I don't need permission :-).
What I asked is whether I should provide:
a) a minimal fix to the issue in this particular change
or
b) send patches that replace this notemt approach with the another
that I believe is better than this one (*)
?
(*) In case you want to see the another approach before answering, it's
part of my RS485 patchset (patches 1-2) [1]. My solution doesn't need
the extra notemt timer and also allows drivers easy access to frame
timing information (rather than them storing it per purpose).
--
i.
[1] https://lore.kernel.org/linux-serial/20220411083321.9131-3-ilpo.jarvinen@xxxxxxxxxxxxxxx/T/#u
