From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: robh@kernel.org, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: serdev Kconfig in v4.11
Date: Tue, 28 Feb 2017 13:34:42 +0100 [thread overview]
Message-ID: <20170228123442.GA4307@amd> (raw)
In-Reply-To: <20170228123037.GA31751@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Tue 2017-02-28 13:30:37, Greg KH wrote:
> On Tue, Feb 28, 2017 at 12:55:26PM +0100, Pavel Machek wrote:
> > Hi!
> >
> > menuconfig SERIAL_DEV_BUS
> > tristate "Serial device bus"
> > help
> > Core support for devices connected via a serial port.
> >
> > This is pretty misleading, it would be nice to mention that this is
> > mostly for embedded devices, and perhaps mention "say N if you don't know".
>
> It's not just for embedded devices, just wait, it will get used
> everywhere :)
Yeah, well. It is "support for automatically attaching devices
attached over serial port". You can support them just fine without
serdev, but you'll have to do irattach/hciattach/whatever attach
manually...
> > config SERIAL_DEV_CTRL_TTYPORT
> > bool "Serial device TTY port controller"
> >
> > I have no idea what this is, please provide some kind of help here.
>
> Patches welcome :)
>
> Seriously, just say N for now, you will be fine. Rob, care to update
> the Kconfig help a bit?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-02-28 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 11:55 serdev Kconfig in v4.11 Pavel Machek
2017-02-28 12:30 ` Greg KH
2017-02-28 12:34 ` Pavel Machek [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=20170228123442.GA4307@amd \
--to=pavel@ucw.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.