[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200219073709.GB2728338@kroah.com>
Date: Wed, 19 Feb 2020 08:37:09 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Vitor Soares <Vitor.Soares@...opsys.com>
Cc: linux-kernel@...r.kernel.org, linux-i3c@...ts.infradead.org,
Joao.Pinto@...opsys.com, Jose.Abreu@...opsys.com,
bbrezillon@...nel.org, wsa@...-dreams.de, arnd@...db.de,
broonie@...nel.org, corbet@....net
Subject: Re: [PATCH v3 4/5] i3c: add i3cdev module to expose i3c dev in /dev
On Wed, Feb 19, 2020 at 01:20:42AM +0100, Vitor Soares wrote:
> +config I3CDEV
> + tristate "I3C device interface"
> + depends on I3C
> + help
> + Say Y here to use i3c-* device files, usually found in the /dev
> + directory on your system. They make it possible to have user-space
> + programs use the I3C devices.
> +
> + This support is also available as a module. If so, the module
> + will be called i3cdev.
> +
> + Note that this application programming interface is EXPERIMENTAL
> + and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
Hah, no, we don't get to say stuff like that. It's hard to write good
apis, but once this is merged, we need to support what is there, right?
kernel programming is hard :(
Powered by blists - more mailing lists