[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4j1NdXs-ng6VBNZ@smile.fi.intel.com>
Date: Thu, 16 Jan 2025 14:01:57 +0200
From: Andy Shevchenko <andy@...nel.org>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Andre Werner <andre.werner@...tec-electronic.com>,
gregkh@...uxfoundation.org, hvilleneuve@...onoff.com,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
lech.perczak@...lingroup.com
Subject: Re: [PATCH v1] serial: sc16is7xx: Extend IRQ check for negative valus
On Thu, Jan 16, 2025 at 11:02:23AM +0100, Jiri Slaby wrote:
> On 16. 01. 25, 10:53, Andy Shevchenko wrote:
> > On Thu, Jan 16, 2025 at 10:42:14AM +0100, Jiri Slaby wrote:
> > > This is threaded weirdly.
> >
> > Yeah, new patch (version) — new email thread.
> >
> > > On 16. 01. 25, 10:32, Andre Werner wrote:
> > > > Fix the IRQ check to treat the negative values as No IRQ.
> > >
> > > Care to describe on what HW that can happen?
> >
> > But how does this relevant? The whole idea is that neither I²C nor SPI
> > frameworks do not guarantee the IRQ field never be negative. This is
> > the fix to the previously submitted patch.
>
> They do AFAICS.
They don't AFAICT.
> Could you be more specific?
The documentation of the fields and their types suggests my way of perception.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists