[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH2PR12MB42169E22641024B57E78CFF2AE100@CH2PR12MB4216.namprd12.prod.outlook.com>
Date: Wed, 19 Feb 2020 08:45:55 +0000
From: Vitor Soares <Vitor.Soares@...opsys.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-i3c@...ts.infradead.org" <linux-i3c@...ts.infradead.org>,
Joao Pinto <Joao.Pinto@...opsys.com>,
Jose Abreu <Jose.Abreu@...opsys.com>,
"bbrezillon@...nel.org" <bbrezillon@...nel.org>,
"wsa@...-dreams.de" <wsa@...-dreams.de>,
"arnd@...db.de" <arnd@...db.de>,
"broonie@...nel.org" <broonie@...nel.org>,
"corbet@....net" <corbet@....net>
Subject: RE: [PATCH v3 4/5] i3c: add i3cdev module to expose i3c dev in /dev
Hi Greg,
From: Greg KH <gregkh@...uxfoundation.org>
Date: Wed, Feb 19, 2020 at 07:37:09
> 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 :(
I will remove this part.
Best regards,
Vitor Soares
Powered by blists - more mailing lists