From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Max Staudt <mstaudt@suse.de>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: option 'force_polling' for buggy IRQs
Date: Thu, 28 Jul 2016 12:01:45 -0400 [thread overview]
Message-ID: <20160728160145.GB27400@thunk.org> (raw)
In-Reply-To: <20160728144704.GA12984@kroah.com>
On Thu, Jul 28, 2016 at 07:47:04AM -0700, Greg KH wrote:
> > I agree, and I thought about it, but since this is meant for a very limited
> > audience, I think a catch-all is the easiest solution - both in terms of
> > implementation as well as ease of use.
> >
> > It's not meant for general consumption anyway.
>
> Then I really don't want to have to maintain and support such a kernel
> option for 20+ years, just because of one broken system out there like
> this. There are workarounds for this, as you have seen, including
> booting with a "real" userspace, so I don't want to take this patch.
One way to make this a bit more general purpose would be too add a way
to configure ttyS0 completely --- e.g., being able to specify the
port, irq, uart type, flags, etc. It still wouldn't be needed except
for very rarely (since either serial ports use self-configuring buses
--- e.g., USB, PCI, etc.) or they use the legacy x86 ports.
So perhaps Greg might be more willing to take that kind of change, but
even then, it could be argued that the maintaining such a kernel
option for just a few non-standard or broken systems is still not
worth it, but it would at least be somewhat more general purpose.
- Ted
next prev parent reply other threads:[~2016-07-28 16:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:36 [PATCH] 8250: option 'force_polling' for buggy IRQs Max Staudt
2016-07-25 17:47 ` Greg KH
2016-07-26 11:42 ` Max Staudt
2016-07-26 15:08 ` Greg KH
2016-07-26 16:18 ` Max Staudt
2016-07-27 12:09 ` One Thousand Gnomes
2016-07-27 12:14 ` Max Staudt
2016-07-27 13:33 ` Theodore Ts'o
2016-07-27 20:01 ` One Thousand Gnomes
2016-07-28 9:59 ` Max Staudt
2016-07-28 14:47 ` Greg KH
2016-07-28 16:01 ` Theodore Ts'o [this message]
2016-07-28 18:40 ` Eric W. Biederman
2016-07-29 9:23 ` One Thousand Gnomes
2016-07-29 9:58 ` Max Staudt
2016-07-29 17:38 ` Eric W. Biederman
2016-08-01 15:27 ` One Thousand Gnomes
2016-07-25 18:19 ` kbuild test robot
2016-07-26 11:47 ` [PATCHv2] " Max Staudt
2016-07-26 11:54 ` [PATCHv3] " Max Staudt
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=20160728160145.GB27400@thunk.org \
--to=tytso@mit.edu \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mstaudt@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).