mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christopher Heiny <cheiny@synaptics.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Allie Xiong <axiong@synaptics.com>,
	William Manson <WManson@synaptics.com>
Subject: Re: [RFC PATCH 1/1] input/touchscreen: Synaptics Touchscreen Driver
Date: Mon, 8 Mar 2010 00:36:06 -0800	[thread overview]
Message-ID: <20100308083605.GC14856@core.coreip.homeip.net> (raw)
In-Reply-To: <4B905B59.8020209@synaptics.com>

On Thu, Mar 04, 2010 at 05:16:09PM -0800, Christopher Heiny wrote:
> On 03/02/2010 01:12 AM, Dmitry Torokhov wrote:
> >Hi Christofer,
> >
> >I assume that since you sent it with git-send-email it was your
> >corporate mail server that murdered all identation and whitespace.
> >Please try sending next version using alternative server, like gmail or
> >maybe your personal account. On the off chance that the formatting used
> >in the driver was preserved intact - please remember that kernel uses
> >hard tabs for identation (8 chars, no expanding). Camel-casing is also
> >frowned upon.
> 
> Actually, the strange indenting/whitespace is due to a day-long struggle
> with checkpatch.pl to get it to accept something - anything - without
> complaining.  Personally I thought the formatting that checkpatch
> finally accepted was kind of strange, but went with it.
> 
> We'll update to 8-space hard tabs only, and ignore any future
> checkpatch complaints in that department.

Umm, generally speaking checkpatch is "telling the truth" and if you run
it aginst most of the krenle code you shold get very few complaints. The
only thing I tend to ignore is the 80 column limit (which I think is
being liften in recent version).

Also, while you are at it - consider using dev_xxx() for printing
messages when you have 'struct device *' available and pr_xxx() when you
do not have it instead of using "naked" printks.

Thanks.

-- 
Dmitry

  reply	other threads:[~2010-03-08  8:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 22:37 [RFC PATCH 0/1] " Christopher Heiny
2010-02-17 22:37 ` Christopher Heiny
2010-02-17 22:37 ` [RFC PATCH 1/1] " Christopher Heiny
2010-03-02  9:12   ` Dmitry Torokhov
2010-03-05  1:16     ` Christopher Heiny
2010-03-08  8:36       ` Dmitry Torokhov [this message]
2010-02-18  9:54 ` [RFC PATCH 0/1] " Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2010-05-29  0:29 Christopher Heiny
2010-05-29  0:29 ` [RFC PATCH 1/1] " Christopher Heiny
2010-05-29 12:32   ` Jean Delvare
2010-05-29 20:34   ` Henrik Rydberg
2010-03-23  2:07 [RFC PATCH 0/1] " Christopher Heiny
2010-03-23  2:07 ` [RFC PATCH 1/1] " Christopher Heiny
2010-04-02 12:50   ` Jean Delvare
2010-04-05 23:04     ` Christopher Heiny
2010-02-02  2:03 [RFC PATCH 0/1] " Christopher Heiny
2010-02-02  2:03 ` [RFC PATCH 1/1] " Christopher Heiny
2009-12-19 20:44 [RFC] [PATCH 0/1] " Christopher Heiny
2009-12-19 20:49 ` [RFC] [PATCH 1/1] " Christopher Heiny
2009-12-20  3:05   ` Dmitry Torokhov
2010-01-03 19:48     ` William Manson
2010-01-03 22:30       ` Dmitry Torokhov
2010-01-05 21:57         ` William Manson
2010-01-05 22:40           ` Dmitry Torokhov
2010-01-06  0:45             ` William Manson

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=20100308083605.GC14856@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=WManson@synaptics.com \
    --cc=axiong@synaptics.com \
    --cc=cheiny@synaptics.com \
    --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

Powered by JetHome