From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Mans Rullgard <mans@mansr.com>, Jiri Slaby <jirislaby@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250: add option to disable registration of legacy ISA ports
Date: Mon, 1 Feb 2021 08:38:43 +0100 [thread overview]
Message-ID: <YBewA7FDXSjR6kIq@kroah.com> (raw)
In-Reply-To: <CAHp75VenDC0R3uX4_=Yzii-q5Z-YWcfT2_OO0yJkYehYAHDCew@mail.gmail.com>
On Sun, Jan 31, 2021 at 09:25:33PM +0200, Andy Shevchenko wrote:
> On Thursday, January 28, 2021, Mans Rullgard <mans@mansr.com> wrote:
>
> > On systems that do not have the traditional PC ISA serial ports, the
> > 8250 driver still creates non-functional device nodes. This change
> > makes only ports that actually exist (PCI, DT, ...) get device nodes.
> >
> >
>
> This is kinda ABI breakage. At least this will break x86 platforms with
> HSUARTs (all modern ones) that are used in embedded systems.
>
> I think you would rather need an option to disable this and select it by
> the platforms where it is known not to break anything.
This option is behind CONFIG_EXPERT, if you set it, you know what you
are doing, so that's fine.
thanks,
greg k-h
next prev parent reply other threads:[~2021-02-01 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 17:22 [PATCH] serial: 8250: add option to disable registration of legacy ISA ports Mans Rullgard
[not found] ` <CAHp75VenDC0R3uX4_=Yzii-q5Z-YWcfT2_OO0yJkYehYAHDCew@mail.gmail.com>
2021-01-31 19:47 ` Måns Rullgård
2021-02-01 7:38 ` Greg Kroah-Hartman [this message]
[not found] ` <YBam2m2VMowH5Yth@kroah.com>
[not found] ` <yw1xwnvtcki0.fsf@mansr.com>
[not found] ` <YBa0J82FrD6mdP/v@kroah.com>
2021-01-31 15:47 ` Måns Rullgård
2021-01-31 15:53 ` Greg Kroah-Hartman
2021-02-18 10:49 ` Maarten Brock
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=YBewA7FDXSjR6kIq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mans@mansr.com \
/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