mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Liviu I." <liviu.i.2222@gmail.com>,
	gregkh@linuxfoundation.org, amk@cray.com, liang.zhen@intel.com,
	uja.ornl@gmail.com, emoly.liu@intel.com,
	rashika.kheria@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: Eudyptula Challenge (Task 10)
Date: Mon, 28 Jul 2014 11:46:55 -0400	[thread overview]
Message-ID: <20140728154655.GV23220@titan.lakedaemon.net> (raw)
In-Reply-To: <20140728125319.GA537@infradead.org>

On Mon, Jul 28, 2014 at 05:53:19AM -0700, Christoph Hellwig wrote:
> Can you folks please stop this challenge Bullshit?  More checkpatch
> fixes is not something we'll need at all.

Greg and Dan have previously said that the staging tree is a good place
for newcomers to submit checkpatch cleanup patches.  However, I think
there are a few tweaks that could be made to the Eudyptula Challenge to
avoid this noise/frustration:

  - No need to send to lkml, the staging tree ML is probably fine.

  - Don't mention Eudyptula Challenge, it's not relevant to the patch.
     * It looks like you want a cookie.  We have none.

  - Submit the patch to the Challenge admins first for review.  This
    patch submission should have never made the cut.
     - No S-o-B
     - MIME attachment
     - Subject line is just wrong
     - Full name missing in From:

I've worked with several participants of the challenge and never saw
this many things wrong with a patch submission.  Either the admins are
dropping the ball, or this participant got loose somehow. :)

It makes me wonder if they should start with a git workflow from day
one?  It would prevent a lot of these avoidable mistakes.

thx,

Jason.

  parent reply	other threads:[~2014-07-28 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  7:13 Liviu I.
2014-07-28  7:37 ` Dan Carpenter
2014-07-28 12:53 ` Christoph Hellwig
2014-07-28 13:58   ` Lucas Tanure
2014-07-28 14:07     ` Denis Kirjanov
2014-07-28 15:46   ` Jason Cooper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-27 19:56 Liviu I.
2014-07-27 20:00 ` Greg KH
     [not found] <Eudyptula Challenge (Task 10)>
2014-06-12 10:35 ` Wahib Faizi

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=20140728154655.GV23220@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=amk@cray.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=emoly.liu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=liang.zhen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.i.2222@gmail.com \
    --cc=rashika.kheria@gmail.com \
    --cc=uja.ornl@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®