From: "Frédéric Danis" <frederic.danis.oss@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Greg Kroah-Hartman <greg@kroah.com>
Cc: Johan Hovold <johan@kernel.org>, Rob Herring <robh@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Loic Poulain <loic.poulain@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Hans de Goede <hdegoede@redhat.com>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] ACPI serdev support
Date: Wed, 18 Oct 2017 16:46:05 +0200 [thread overview]
Message-ID: <ac53458d-c910-2d0a-a2ad-e7d21f8a5be7@gmail.com> (raw)
In-Reply-To: <AA38D4FD-5A35-460D-85CF-380BAB933448@holtmann.org>
Hi Greg, Rafael, Marcel,
Le 11/10/2017 à 20:32, Marcel Holtmann a écrit :
> Hi Greg,
>
>>>> Add ACPI support for serial attached devices.
>>>>
>>>> Currently, serial devices are not set as enumerated during ACPI scan for SPI
>>>> or i2c buses (but not for UART). This should also be done for UART serial
>>>> devices.
>>>> I renamed *spi_i2c_slave* to *serial_bus_slave* to reflect this.
>>>>
>>>> This needs Johan Hovold's "serdev: fix registration of second slave" patch.
>>> In theory this series could go in through the acpi-tree without my
>>> fix. It would only affect an error case where an unlikely failure to
>>> register an ACPI serdev device, would prevent the tty-class device from
>>> being registered instead of the controller. That is, something we can
>>> live with until this all converges in 4.15-rc1 if needed.
>>>
>>> That said, I think we should consider taking all serdev changes, and
>>> therefore also the ACPI patch, through the tty tree instead in order to
>>> avoid merge conflicts. Rafael?
>> OK
>>
>> Please feel free to add
>>
>> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>
>> to the ACPI core change.
>>
>> And I will assume that this series will go in via the tty tree.
> you have to take these two patches now via the TTY tree now. In case you already marked them as someone else problem ;)
>
> Regards
>
> Marcel
Is there any problem I missed with those patches?
Do I have to re-send them?
Regards,
Fred
next prev parent reply other threads:[~2017-10-18 14:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:32 [PATCH v3 0/2] ACPI serdev support Frédéric Danis
[not found] ` <1507710734-32520-1-git-send-email-frederic.danis.oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-11 8:32 ` [PATCH v3 1/2] serdev: Add ACPI support Frédéric Danis
2017-10-11 8:43 ` Johan Hovold
2017-10-11 8:32 ` [PATCH v3 2/2] ACPI / scan: Fix enumeration for special UART devices Frédéric Danis
2017-10-15 9:57 ` Lukas Wunner
[not found] ` <1507710734-32520-3-git-send-email-frederic.danis.oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-31 14:21 ` [v3,2/2] " Graeme Gregory
2018-02-02 10:03 ` Frédéric Danis
2017-10-11 9:03 ` [PATCH v3 0/2] ACPI serdev support Johan Hovold
2017-10-11 13:09 ` Rafael J. Wysocki
2017-10-11 18:32 ` Marcel Holtmann
2017-10-18 14:46 ` Frédéric Danis [this message]
2017-10-18 14:56 ` Greg Kroah-Hartman
[not found] ` <20171018145608.GB27138-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-10-19 14:23 ` Johan Hovold
2017-10-19 14:26 ` Hans de Goede
2017-10-19 14:32 ` Marcel Holtmann
2017-10-19 14:56 ` Hans de Goede
[not found] ` <CAMZdPi_ZpNrdjJPnS_rQ9t3oYe6+en9oHQMjmMjx_xHL-WWZKQ@mail.gmail.com>
[not found] ` <CAMZdPi_ZpNrdjJPnS_rQ9t3oYe6+en9oHQMjmMjx_xHL-WWZKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-19 18:50 ` Hans de Goede
2017-10-19 19:00 ` Marcel Holtmann
[not found] ` <FFD85CA6-6BD9-45AA-B3C2-898212711C0C-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2017-10-19 19:05 ` Hans de Goede
2017-10-21 9:59 ` Johan Hovold
[not found] ` <877ea825-eec5-d982-f962-d67067749009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-19 14:32 ` 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=ac53458d-c910-2d0a-a2ad-e7d21f8a5be7@gmail.com \
--to=frederic.danis.oss@gmail.com \
--cc=greg@kroah.com \
--cc=hdegoede@redhat.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).