Thread (22 messages) 22 messages, 6 authors, 2017-10-18

Re: Two rtlwifi drivers?

From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: 2017-10-12 10:34:50
Also in: kernel-janitors

On Thu, Oct 12, 2017 at 11:38:06AM +0300, Kalle Valo wrote:
quoted
So what to do?  Any ideas?  What makes your life easier?  You can just
ignore the staging tree, as it should not affect your portion of the
kernel at all, right?
Yes, I automatically ignore anything staging related. But the problem is
that we now have two drivers with the same name and people don't always
remember to prefix the patch with "staging: ". So on a bad day I might
accidentally apply a patch which was meant for your tree. Of course I
immediately revert it as soon as I, or someone else, catches that but
annoying still.
It doesn't bother me if you apply staging patches, I can handle the
merge issues :)
I think we have two options here:

1) We set a deadline (like 12 months or something) for the
   drivers/staging/rtlwifi and after that you refuse to take any patches
   for it. Hopefully this makes it clear for everyone that this fork is
   just temporary. I think Larry is trying to do this, which is great.
Fine with me, if Larry is ok with it.
2) We move the whole rtlwifi driver to staging. A very bad option but
   still better than forking the drivers.
Ick, I don't want that to have to happen, that would not be good for the
users of other devices that the "real" rtlwifi driver supports.

thanks,

greg k-h
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help