public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Williams <unixed@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: ni_at_a2150: Remove a few superfluous braces
Date: Thu, 12 Sep 2013 14:50:12 -0700	[thread overview]
Message-ID: <20130912215012.GA6433@kroah.com> (raw)
In-Reply-To: <1378594294-13653-1-git-send-email-unixed@gmail.com>

On Sat, Sep 07, 2013 at 03:51:34PM -0700, Sean Williams wrote:
> Please don't flame me :) I'm getting my feet wet with kernel contribution.

Why would we flame anyone for sending us patches?

It's as if we are bunch of scary people or something...

Nice job with this, I'll queue it up after 3.12-rc1 is out.

thanks,

greg k-h

      parent reply	other threads:[~2013-09-12 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 22:51 [PATCH] Staging: Remove a few superfluous braces Sean Williams
2013-09-09  9:22 ` Ian Abbott
2013-09-12 21:50 ` Greg KH [this message]

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=20130912215012.GA6433@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=unixed@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