Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1321539 > unrolled thread

Re: wireless-drivers: random cleanup patches piling up

Started byKalle Valo <kvalo@codeaurora.org>
First post2016-01-29 09:10 +0100
Last post2016-02-01 09:30 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: wireless-drivers: random cleanup patches piling up Kalle Valo <kvalo@codeaurora.org> - 2016-01-29 09:10 +0100
    Re: wireless-drivers: random cleanup patches piling up Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-02-01 05:50 +0100
      Re: wireless-drivers: random cleanup patches piling up Kalle Valo <kvalo@codeaurora.org> - 2016-02-01 09:30 +0100

#1321539 — Re: wireless-drivers: random cleanup patches piling up

FromKalle Valo <kvalo@codeaurora.org>
Date2016-01-29 09:10 +0100
SubjectRe: wireless-drivers: random cleanup patches piling up
Message-ID<qWchX-8kA-1@gated-at.bofh.it>
Sudip Mukherjee <sudipm.mukherjee@gmail.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

[toc] | [next] | [standalone]


#1322823

FromSudip Mukherjee <sudipm.mukherjee@gmail.com>
Date2016-02-01 05:50 +0100
Message-ID<qXeB4-5Iz-1@gated-at.bofh.it>
In reply to#1321539
On Fri, Jan 29, 2016 at 10:08:23AM +0200, Kalle Valo wrote:
> Sudip Mukherjee <sudipm.mukherjee@gmail.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.

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

[toc] | [prev] | [next] | [standalone]


#1322892

FromKalle Valo <kvalo@codeaurora.org>
Date2016-02-01 09:30 +0100
Message-ID<qXi1Y-8lp-23@gated-at.bofh.it>
In reply to#1322823
Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:

> 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.

They are in deferred state. The search functionality in patchwork is not
that intuitive and they are not easy to find so here's a direct link:

https://patchwork.kernel.org/project/linux-wireless/list/?state=10&order=date

-- 
Kalle Valo

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web