linux-kernel - Re: [char-misc-next] mei: gsc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y9OUS7Y57t0y0gx4@kroah.com>
Date:   Fri, 27 Jan 2023 10:07:23 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     "Winkler, Tomas" <tomas.winkler@...el.com>
Cc:     "Usyskin, Alexander" <alexander.usyskin@...el.com>,
        "Lubart, Vitaly" <vitaly.lubart@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [char-misc-next] mei: gsc_proxy: add gsc proxy driver

On Tue, Jan 24, 2023 at 09:05:19PM +0000, Winkler, Tomas wrote:
> 
> 
> > -----Original Message-----
> > From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > Sent: Thursday, January 19, 2023 18:21
> > To: Usyskin, Alexander <alexander.usyskin@...el.com>
> > Cc: Winkler, Tomas <tomas.winkler@...el.com>; Lubart, Vitaly
> > <vitaly.lubart@...el.com>; linux-kernel@...r.kernel.org
> > Subject: Re: [char-misc-next] mei: gsc_proxy: add gsc proxy driver
> > 
> > On Wed, Dec 28, 2022 at 11:46:36AM +0000, Usyskin, Alexander wrote:
> > > >
> > > > Why a whole new subdirectory for a tiny 200 line file?
> > > >
> > > All drivers for devices on mei bus have private subdirectory.
> > > This one just modelled on the existing examples.
> > > If you say that this is not a good thing - can put it in the main mei directory.
> > 
> > Put it in the main mei directory, no need to split things up for no good
> > reason.
> > 
> 
> All mei sub drivers are in sperate directories, this driver is indeed tiny, but I do prefer consistency,
> In my view it is easier to maintain that way. 

Ok.

> I believe all the bellow stuff you've already discussed in ths thread,.
> https://lore.kernel.org/lkml/YkXdgQH1GWCitf0A@kroah.com/T/
> I guess all that was explained there, so no need to repeat.
> 
> We'll try to see what can be done to make it more robust and your comments are more than valid,
> but as the thread concludes probably the component framework needs to be addressed. 

Agreed, something needs to be done, you can't make these random
assumptions about the exact driver and device topology as that is not
how the driver model works at all (nor do you want it to work that way.)

thanks,

greg k-h