From: Ian W MORRISON <ianwmorrison@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>,
"Johan Hovold" <johan@kernel.org>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"bluez mailin list (linux-bluetooth@vger.kernel.org)"
<linux-bluetooth@vger.kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Frédéric Danis" <frederic.danis.oss@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Loic Poulain" <loic.poulain@gmail.com>,
"Lukas Wunner" <lukas@wunner.de>,
linux-serial@vger.kernel.org, linux-acpi@vger.kernel.org,
"Greg Kroah-Hartman" <greg@kroah.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] serdev: Update drivers/tty/serdev/Kconfig for ACPI support
Date: Sun, 8 Oct 2017 14:20:33 +1100 [thread overview]
Message-ID: <df3c9f2c-ffb0-35ab-4fa6-e19032b25214@gmail.com> (raw)
In-Reply-To: <8D8274B0-4EF6-41A0-8B76-95023F6DD26C@holtmann.org>
On 10/8/17 6:57 AM, Marcel Holtmann wrote:
> Hi Johan,
>
>>> The current Kconfig for serdev is not compatible when adding ACPI support as it does not work when built as a module as it requires config SERIAL_DEV_CTRL_TTYPORT to be set. This patch makes serdev compiled into the kernel if selected so that config SERIAL_DEV_CTRL_TTYPORT can be correctly set if requiring ACPI support.
<snip>
>> I understand why you want this (to prevent hci_bcm from breaking), but we
>> should generally not have new entries default to y.
>>
<snip>
>> It may be better to have BT_HCIUART_BCM depend on (or select?)
>> SERIAL_DEV_CTRL_TTYPORT instead.
>
> if we move SERIAL_DEV_BUS to bool, then I would just have it be selected by BT_HCIUART_BCM. Frankly the SERIAL_DEV_BUS option is pretty hard to find in the kernel config. And if we depend on TTY, but then select SERIAL_DEV_BUS, I think that is a good compromise.
>
> Regards
>
> Marcel
>
Hi,
Many thanks for everyone's comments on my earlier patch to Kconfigs for ACPI serdev support.
I've submitted a revised patch set which addresses the points raised by making BT_HCIUART_BCM dependent on SERIAL_DEV_CTRL_TTYPORT which in turn is dependent on SERIAL_DEV_BUS and ensures that if SERIAL_DEV_BUS is selected is the code is build it.
Please can you review and let me know if any further changes are required?
Regards,
Ian
next prev parent reply other threads:[~2017-10-08 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 6:16 [PATCH] serdev: Update drivers/tty/serdev/Kconfig for ACPI support Ian W MORRISON
[not found] ` <a4051ac2-1156-751d-ec16-2dbbb30b9258-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-07 6:41 ` Greg Kroah-Hartman
2017-10-07 6:42 ` Marcel Holtmann
[not found] ` <D567DA4A-4443-4A88-B078-50EE458C822A-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2017-10-07 12:06 ` Ian W MORRISON
2017-10-07 15:24 ` Johan Hovold
2017-10-07 19:57 ` Marcel Holtmann
2017-10-08 3:20 ` Ian W MORRISON [this message]
2017-10-09 7:47 ` Johan Hovold
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=df3c9f2c-ffb0-35ab-4fa6-e19032b25214@gmail.com \
--to=ianwmorrison@gmail.com \
--cc=frederic.danis.oss@gmail.com \
--cc=greg@kroah.com \
--cc=gustavo@padovan.org \
--cc=hdegoede@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=johan@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=loic.poulain@gmail.com \
--cc=lukas@wunner.de \
--cc=marcel@holtmann.org \
--cc=rafael@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 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).