Thread (2 messages) 2 messages, 2 authors, 2016-02-01

Re: wireless-drivers: random cleanup patches piling up

From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Date: 2016-02-01 04:41:51
Also in: kernel-janitors, lkml

Possibly related (same subject, not in this thread)

On Fri, Jan 29, 2016 at 10:08:23AM +0200, Kalle Valo wrote:
Sudip Mukherjee [off-list ref] writes:
quoted
quoted
quoted
quoted
That's also my experience from maintaining wireless-drivers for a year,
this seems to be a "hit and run" type of phenomenon.
Should we be looking for someone to run a "wireless-driver-cleanups"
tree?  They could handle the cleanups and trivial stuff, and send
you a pull request a couple of times per release...?
Not a bad idea! But I don't think we need a separate tree as applying
patches from patchwork is easy. It should be doable that we add an
account to patchwork and whenever I see a this type of trivial cleanup
patch I'll assign it to the cleanup maintainer and whenever he/she
thinks it's ready he assigns the patch back to me and I'll apply it.

The only difficult part is finding a victim/volunteer to
do that ;)
I can be a volunteer (victim?). Though i donot know much about
wireless-drivers, but I do know a little about cleanup patches.
And maybe, in the process I will start knowing wireless-drivers.
I think it's better that you have prior experience with linux-wireless
before doing something like this. You can start by reviewing patches and
providing Reviewed-by tags.
Sure, I am starting that way. I checked in patchwork and I do not see
any checkpatch related patch pending (except staging, which Greg will
handle). I think you must have cleared all of them.

regards
sudip
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help