[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CWLP265MB19727D19DE7D0498EEB2B1E4E0390@CWLP265MB1972.GBRP265.PROD.OUTLOOK.COM>
Date: Thu, 24 Sep 2020 17:24:14 +0000
From: Srinivasan Raju <srini.raju@...elifi.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Mostafa Afgani <mostafa.afgani@...elifi.com>,
information <info@...elifi.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH] staging: Initial driver submission for pureLiFi devices
>> --- /dev/null
>> +++ b/drivers/staging/purelifi/TODO
>> @@ -0,0 +1,5 @@
>> +TODO:
>> + - checkpatch.pl cleanups
>> +
>> +Please send any patches or complaints about this driver to pureLiFi Ltd
>> +<info@...elifi.com>
>Why not just do these fixups on your own right now and submit it to the
>"real" part of the kernel? That should take what, a day or so max?
>Just sending stuff to staging because you don't want to do coding style
>cleanups feels very odd. It takes much more work and energy to do it
>this way than to just do it right the first time and get it merged to
>the networking subsystem, right?
>So why do you want to send it to staging?
Thanks for the comments Greg, This is my first kernel patch, I was under
the impression that the staging area is the place to start for any new "Driver" code
We will do the fixes and send an updated patch
Thanks
Srini
Powered by blists - more mailing lists