[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bn84kdu0.fsf@kamboji.qca.qualcomm.com>
Date: Fri, 29 Jan 2016 10:08:23 +0200
From: Kalle Valo <kvalo@...eaurora.org>
To: Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc: "John W. Linville" <linville@...driver.com>,
Joe Perches <joe@...ches.com>, linux-wireless@...r.kernel.org,
kbuild test robot <lkp@...el.com>,
kernel-janitors <kernel-janitors@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: wireless-drivers: random cleanup patches piling up
Sudip Mukherjee <sudipm.mukherjee@...il.com> writes:
>> >> 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.
--
Kalle Valo
Powered by blists - more mailing lists