linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Baodong Chen <chenbdchenbd@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixed coding style issues
Date: Sun, 29 Jul 2012 22:53:41 -0700	[thread overview]
Message-ID: <20120730055341.GC5830@core.coreip.homeip.net> (raw)
In-Reply-To: <1343200277-14385-1-git-send-email-chenbdchenbd@gmail.com>

Hi Baodong,

On Wed, Jul 25, 2012 at 03:11:17PM +0800, Baodong Chen wrote:
> Fexed coding style issues from scripts/checkpatch.pl in drivers/input
> 

Thank you for your patch. I picked up the parts that made sense and
dropped the rest.

Thanks.

-- 
Dmitry

      parent reply	other threads:[~2012-07-30  5:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25  7:11 [PATCH] fixed coding style issues Baodong Chen
2012-07-25  7:30 ` Joe Perches
2012-07-25  7:44   ` Baodong Chen
2012-07-25  8:01     ` Joe Perches
2012-07-25  8:25       ` Baodong Chen
2012-07-30  5:53 ` Dmitry Torokhov [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=20120730055341.GC5830@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=chenbdchenbd@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).