[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a77d53966d117bc5c7ff2836634d8591633f4f5.camel@hadess.net>
Date: Fri, 10 May 2019 11:35:58 +0200
From: Bastien Nocera <hadess@...ess.net>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Jonathan Cameron <jic23@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Eric Piel <eric.piel@...mplin-utc.net>,
linux-input@...r.kernel.org, letux-kernel@...nphoenux.org,
kernel@...a-handheld.com, Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [RFC v2] iio: input-bridge: optionally bridge iio acceleometers
to create a /dev/input interface
On Fri, 2019-05-10 at 11:33 +0200, H. Nikolaus Schaller wrote:
> >
<snip>
> It does through "Input device name:" starting with "iio-bridge:" as
> you can see in the commit message of [RFC v3]:
This makes it ABI, right?
Big fat warnings around the code that declares it would be appreciated.
Powered by blists - more mailing lists