Hi Kalle,
On Wed, Mar 16, 2016 at 8:42 PM, Julian Calaby wrote:
> Hi Kalle,
>
> On Wed, Mar 16, 2016 at 8:22 PM, Kalle Valo wrote:
>> Julian Calaby writes:
>>
>>> Hi Kalle,
>>>
>>> On Mon, Feb 1, 2016 at 7:21 PM, Kalle Valo wrote:
Sudip Mukherjee writes:
> Sure, I am starting th
Hi Kalle,
On Wed, Mar 16, 2016 at 8:22 PM, Kalle Valo wrote:
> Julian Calaby writes:
>
>> Hi Kalle,
>>
>> On Mon, Feb 1, 2016 at 7:21 PM, Kalle Valo wrote:
>>> Sudip Mukherjee writes:
>>>
Sure, I am starting that way. I checked in patchwork and I do not see
any checkpatch related pat
Julian Calaby writes:
> Hi Kalle,
>
> On Mon, Feb 1, 2016 at 7:21 PM, Kalle Valo wrote:
>> Sudip Mukherjee 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
Hi Kalle,
On Mon, Feb 1, 2016 at 7:21 PM, Kalle Valo wrote:
> Sudip Mukherjee 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.
>
> The
Sudip Mukherjee 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
t
On Fri, Jan 29, 2016 at 10:08:23AM +0200, Kalle Valo wrote:
> Sudip Mukherjee 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-dr
Sudip Mukherjee 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 st
On Fri, Jan 22, 2016 at 05:54:12PM +0200, Kalle Valo wrote:
> "John W. Linville" writes:
>
> > On Fri, Jan 22, 2016 at 02:21:20PM +0200, Kalle Valo wrote:
> >> Joe Perches writes:
> >>
> >> > On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
> >> >> Hi,
> >> >>
> >> >> I have quite a lot of
On Fri, 2016-01-22 at 10:12 -0500, John W. Linville wrote:
> On Fri, Jan 22, 2016 at 02:21:20PM +0200, Kalle Valo wrote:
> > Joe Perches writes:
> >
> > > On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
> > > > Hi,
> > > >
> > > > I have quite a lot of random cleanup patches from new develo
"John W. Linville" writes:
> On Fri, Jan 22, 2016 at 02:21:20PM +0200, Kalle Valo wrote:
>> Joe Perches writes:
>>
>> > On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
>> >> Hi,
>> >>
>> >> I have quite a lot of random cleanup patches from new developers waiting
>> >> in my queue:
>> >>
On Fri, Jan 22, 2016 at 02:21:20PM +0200, Kalle Valo wrote:
> Joe Perches writes:
>
> > On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
> >> Hi,
> >>
> >> I have quite a lot of random cleanup patches from new developers waiting
> >> in my queue:
> >>
> >> https://patchwork.kernel.org/proje
Hi Kalle,
On Fri, Jan 22, 2016 at 11:17 PM, Kalle Valo wrote:
> Julian Calaby writes:
>
>> Hi Kalle,
>>
>> On Fri, Jan 22, 2016 at 1:58 AM, Kalle Valo wrote:
>>> Hi,
>>>
>>> I have quite a lot of random cleanup patches from new developers waiting
>>> in my queue:
>>>
>>> https://patchwork.kerne
Joe Perches writes:
> On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
>> Hi,
>>
>> I have quite a lot of random cleanup patches from new developers waiting
>> in my queue:
>>
>> https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
>>
>> (Not all of
Julian Calaby writes:
> Hi Kalle,
>
> On Fri, Jan 22, 2016 at 1:58 AM, Kalle Valo wrote:
>> Hi,
>>
>> I have quite a lot of random cleanup patches from new developers waiting
>> in my queue:
>>
>> https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
>>
>>
Larry Finger writes:
> We might get new developers, but the cost may be high. In the staging
> tree, things are worse. The tools can be applied in a blind fashion,
> but the results can be really stupid. GregKH has told a few would-be
> contributors to "go away" after a few patches that would not
On Thu, Jan 21, 2016 at 04:52:45PM -0800, Joe Perches wrote:
> Whitespace patches, where git diff -w does not show
> any difference and objdiff on the objects for a few
> randconfigs are identical, maybe could be sifted
> into a separate category from other patches.
> Maybe the kbuild test robot co
On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
> Hi,
>
> I have quite a lot of random cleanup patches from new developers waiting
> in my queue:
>
> https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
>
> (Not all of them are cleanup patches, there
Hi Kalle,
On Fri, Jan 22, 2016 at 1:58 AM, Kalle Valo wrote:
> Hi,
>
> I have quite a lot of random cleanup patches from new developers waiting
> in my queue:
>
> https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
>
> (Not all of them are cleanup patches,
On 01/21/2016 08:58 AM, Kalle Valo wrote:
Hi,
I have quite a lot of random cleanup patches from new developers waiting
in my queue:
https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
(Not all of them are cleanup patches, there are also few patches
defe
Hi,
I have quite a lot of random cleanup patches from new developers waiting
in my queue:
https://patchwork.kernel.org/project/linux-wireless/list/?state=10&delegate=25621&order=date
(Not all of them are cleanup patches, there are also few patches
deferred due to other reasons, but you get the i
20 matches
Mail list logo
