Bad Patches and Issues with other devolopers

[Nick Krause]

On Tue, Aug 5, 2014 at 1:59 PM, Mandeep Sandhu
<mandeepsandhu.chd at gmail.com> wrote:
> Hi Nick,
>
> I came across some G+ posts from kernel developers discussing you and
> your recent patch submissions. I must say you're pretty (in)famous! :)
>
> Jokes aside, why not just follow on the advice given to you by so many
> people, i.e pick an area of interest (in the various kernel
> subsystems) for yourself, first pick really small ossues (but not the
> code formatting ones as they only tend to generate noise for the
> maintainer and not really fix anything), create the patch, see if the
> kernel builds with. TEST IT, most importantly (if you don't have the
> requisite hw then either acquire one, or pick another issue where you
> CAN test it). Basically check everything thats mentioned here:
>
> https://www.kernel.org/doc/Documentation/SubmittingPatches
> http://kernelnewbies.org/OPWfirstpatch
>
> Trust me, if you _do_ go through this process and submit a 'good'
> patch, all past issues that you've had with other developers will be
> forgotten.
>
> Don't be in a rush to get 'something' in the kernel. I know its a big
> deal to get things in one of the coolest piece of software on this
> planet, but you'll need a lot perseverance and patience to be a kernel
> contributor.
>
> HTH,
> -mandeep
>
>
> On Tue, Aug 5, 2014 at 10:42 AM, Nick Krause <xerofoify at gmail.com> wrote:
>> I have sent out just ten bad patches and the developers seem very
>> annoyed with me and
>> think I am trolling. If someone on this list can find a way for me to
>> improve my relationship
>> with them and let me continue my work here that would be great.
>> Nick
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


That's fine,
I feel perhaps I am just really trying to force my code in(ego) and
just is bad form.
If anyone on this list can read my last trace to check my logic first,
before I write
a patch and let you check it, that would be great.
Thanks A lot,
Nick