On Mon, Aug 4, 2014 at 1:43 AM, Nick Krause <xerofoify@xxxxxxxxx> wrote: > On Mon, Aug 4, 2014 at 1:38 AM, Dave Airlie <airlied@xxxxxxxxx> wrote: >> On 4 August 2014 15:03, Hans Verkuil <hverkuil@xxxxxxxxx> 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@xxxxxxxxx> >>> >>> 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 Dave, I understand your issues with my programming. I need to try and understand the kernel first before programming for it. Regards Nick -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
