All of lore.kernel.org
 help / color / mirror / Atom feed
From: carlo@caione.org (Carlo Caione)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Checkpatch Patches
Date: Tue, 16 Sep 2014 17:50:23 +0200	[thread overview]
Message-ID: <CAOQ7t2aJxKUCkEmNOrdPKqU-zrOcNABTNyKKBvYoyNZoGu5G8g@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVi5CL4b_YpcnDJ2yL-7YXUy+VtH23+jo0NY_Xs=15OdCA@mail.gmail.com>

On Tue, Sep 16, 2014 at 5:44 PM, Nick Krause <xerofoify@gmail.com> wrote:
> On Tue, Sep 16, 2014 at 10:19 AM,  <Valdis.Kletnieks@vt.edu> wrote:
>> On Tue, 16 Sep 2014 08:44:27 -0400, nick said:
>>
>>> I am attaching two check patch patches I wrote in the last few days as I am unable to get a reply
>>> from the maintainers. Would someone please send them off for me.
>>
>> "I am attaching".  Fail 3 words in.
>>
>> That's why you aren't getting a reply from the maintainers. They don't bother
>> reading patches they know will probably *never* be correct.
>>
>> And yes, at least one of the two patches is incorrect.
>>
>>>> Thanks for the Help, I really do appreciate it and I do understand how much I have screwed up. My concern now is
>>>> now to make it right.
>>
>> You don't make it right by posting more wrong patches. Now do us
>> all a favor and *stop* being either an idiot, or a troll, or whatever
>> your problem is.  We have *zero* desire to see *any* more patches from
>> somebody who is either unable or unwilling to post a *single* correct
>> patch after *two months* of trying.
>>
>> So please do us a favor and go piss off some other open source project.
>>
>> THE KERNEL DOES NOT WANT YOUR BULLSHIT.
>>
>>
>>
> I am going to attach it again and I understand Valdis. I am going to
> talk to Sudip about reading and checking
> my patches first.

Rik,
probably it's time to ban Nick also from this ml.

-- 
Carlo Caione

  reply	other threads:[~2014-09-16 15:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 12:44 Checkpatch Patches nick
2014-09-16 12:47 ` Kristofer Hallin
2014-09-16 12:50   ` nick
2014-09-16 13:06 ` Sudip Mukherjee
2014-09-16 13:11   ` nick
2014-09-16 13:21     ` Sudip Mukherjee
2014-09-16 13:26       ` nick
     [not found]         ` <CADVatmOZx7q636=b0pQ95CZ93_6jn_jZ2SCPKH7pHmw9P0mRuQ@mail.gmail.com>
     [not found]           ` <54183C0A.80409@gmail.com>
     [not found]             ` <CADVatmP1G1pg-vDmn1z-vg9Ppn7Yhvc=hnhbaOyENbdg6WUO2A@mail.gmail.com>
2014-09-16 13:47               ` Sudip Mukherjee
2014-09-16 13:07 ` Robert P. J. Day
2014-09-16 13:13 ` Robert P. J. Day
2014-09-16 14:19 ` Valdis.Kletnieks at vt.edu
2014-09-16 15:44   ` Nick Krause
2014-09-16 15:50     ` Carlo Caione [this message]
2014-09-16 15:57       ` Lidza Louina
2014-09-16 16:08         ` Valdis.Kletnieks at vt.edu
2014-09-16 16:14           ` Robert P. J. Day
2014-09-16 16:11         ` Robert P. J. Day
2014-09-16 16:10     ` Hugo Mills
2014-09-16 16:57     ` Sudip Mukherjee
2014-09-16 17:12       ` Nick Krause
2014-09-16 17:27         ` Robert P. J. Day
2014-09-16 17:27         ` Valdis.Kletnieks at vt.edu
2014-09-16 17:28         ` Rik van Riel
2014-09-16 17:39           ` Valdis.Kletnieks at vt.edu
2014-09-16 18:29             ` Nick Krause
2014-09-16 18:36               ` Kristofer Hallin
2014-09-16 18:44                 ` Rik van Riel
2014-09-16 19:30                   ` Robert P. J. Day
2014-09-16 18:45               ` Mandeep Sandhu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOQ7t2aJxKUCkEmNOrdPKqU-zrOcNABTNyKKBvYoyNZoGu5G8g@mail.gmail.com \
    --to=carlo@caione.org \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.