From: Greg KH <gregkh@linuxfoundation.org>
To: Maarten Brock <Maarten.Brock@sttls.nl>
Cc: Andre Werner <andre.werner@systec-electronic.com>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"hvilleneuve@dimonoff.com" <hvilleneuve@dimonoff.com>,
"andy@kernel.org" <andy@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"lech.perczak@camlingroup.com" <lech.perczak@camlingroup.com>
Subject: Re: [External Email] Re: [PATCH] serial: sc16is7xx: Add polling feature if no IRQ usage possible
Date: Mon, 23 Dec 2024 18:59:19 +0100 [thread overview]
Message-ID: <2024122301-trickery-unexpired-e6b6@gregkh> (raw)
In-Reply-To: <AS8PR05MB9810B543A1223ED04729EAAE83022@AS8PR05MB9810.eurprd05.prod.outlook.com>
On Mon, Dec 23, 2024 at 02:27:22PM +0000, Maarten Brock wrote:
> > I got your point and I'm fully with. This caused me to print a warning
> > in Kernel log because it should not be the general working method.
> > In our special case we do not have any other option because the sensor
> > module using the SC16IS7xx and the hardware with the MCU running Linux OS
> > are fixed. We had no possibilities to move any GPIO or such. This was
> > the only chance to support the dedicated sensor platform and I may be
> > the case that someone else faces the same problems. I thought that
> > someone else may benefit from this workaround too. But as I got your
> > point I'm also fine if it is not merged into main Linux Kernel sources.
>
> I vote this patch to go in (after modification).
Ok, let's see a cleaned up version of this and we'll review it again.
thanks,
greg k-h
prev parent reply other threads:[~2024-12-23 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 8:46 [PATCH] serial: sc16is7xx: Add polling feature if no IRQ usage possible Andre Werner
2024-12-19 8:56 ` Greg KH
2024-12-19 9:22 ` [External Email] " Andre Werner
2024-12-19 9:41 ` Greg KH
2024-12-20 5:50 ` Andre Werner
2024-12-23 14:27 ` Maarten Brock
2024-12-23 17:59 ` Greg KH [this message]
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=2024122301-trickery-unexpired-e6b6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Maarten.Brock@sttls.nl \
--cc=andre.werner@systec-electronic.com \
--cc=andy@kernel.org \
--cc=hvilleneuve@dimonoff.com \
--cc=jirislaby@kernel.org \
--cc=lech.perczak@camlingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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