[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1ED14975-FC0C-44AB-8F05-782DBC9E98F8@goldelico.com>
Date: Thu, 18 Aug 2016 12:54:15 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Pavel Machek <pavel@....cz>
Cc: Rob Herring <robh@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marcel Holtmann <marcel@...tmann.org>,
Jiri Slaby <jslaby@...e.com>,
Sebastian Reichel <sre@...nel.org>,
Peter Hurley <peter@...leysoftware.com>,
NeilBrown <neil@...wn.name>, Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...aro.org>,
linux-bluetooth@...r.kernel.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] UART slave device bus
Hi Pavel,
> Am 18.08.2016 um 12:47 schrieb Pavel Machek <pavel@....cz>:
>
>
>>
>> Thereof 4 files, ~260 changes w/o gps demo and documentation/bindings.
>
> So what do you use for the serial devices? platform_device was vetoed
> for that purpose by Greg.
device tree?
This adds code of course - but only for the slave drivers. So you shouldn't count
them for a fair comparison of what it means for implementing a new API.
Powered by blists - more mailing lists