linux-kernel - Re: [PATCH] v4l2: Change call of function in videobuf2-core.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Aug 2014 01:43:12 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	Dave Airlie <airlied@...il.com>
Cc:	Hans Verkuil <hverkuil@...all.nl>,
	Udo van den Heuvel <udovdh@...all.nl>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] v4l2: Change call of function in videobuf2-core.c

On Mon, Aug 4, 2014 at 1:38 AM, Dave Airlie <airlied@...il.com> wrote:
> On 4 August 2014 15:03, Hans Verkuil <hverkuil@...all.nl> wrote:
>> On 08/04/2014 05:25 AM, Nicholas Krause wrote:
>>> This patch changes the call of vb2_buffer_core to use VB2_BUFFER_STATE_ACTIVE
>>> inside the for instead of not setting in correctly to VB2_BUFFER_STATE_ERROR.
>>>
>>> Signed-off-by: Nicholas Krause <xerofoify@...il.com>
>>
>> Dunno what's going on here after reading Dave Airlie's reply, but:
>>
>
> Nick has decided he wants to be a kernel developer, a laudable goal.
>
> He however has decided not to take any advice given to me by a number of other
> kernel developers on how to work on the kernel. So instead he sends random
> broken patches to random subsystems in the hope that one will slip past a sleepy
> maintainer and end up in the kernel.
>
> He isn't willing to spend his own time learning anything, he is
> expecting that kernel
> developers want to spoon feed someone who sends them broken patches.
>
> We've asked him to stop, he keeps doing it, then when caught out apologizes
> with something along the lines, of I'm trying to learn, "idiot
> mistake", despite having
> been told to take a step back and try and learn how the kernel works.
>
> Now we have to waste more maintainer time making sure nobody accidentally
> merges anything he sends.
>
> Dave.
All of my merges are not in the main kernel and have been revoked.
Cheers Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/