linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"greg@kroah.com" <greg@kroah.com>,
	"eric.piel@tremplin-utc.net" <eric.piel@tremplin-utc.net>,
	"broonie@opensource.wolfsonmicro.com" 
	<broonie@opensource.wolfsonmicro.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital
Date: Tue, 17 Jan 2012 15:47:02 -0800	[thread overview]
Message-ID: <20120117154702.d009df12.akpm@linux-foundation.org> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13177CDA4@DBDE01.ent.ti.com>

On Tue, 17 Jan 2012 07:32:47 +0000
"AnilKumar, Chimata" <anilkumar@ti.com> wrote:

> Hi All,
> 
> Recalling the patch, provide the comments if there are any if not please include
> this patch to v3.3 kernel.

The patch is all mangled by someone's email client.  Wordwrapping, mime
crap which my MUA can't decrypt, etc.

> -----Original Message-----
> From: AnilKumar, Chimata 
> Sent: Friday, December 23, 2011 10:55 AM
> To: arnd@arndb.de; greg@kroah.com; eric.piel@tremplin-utc.net; akpm@linux-foundation.org; broonie@opensource.wolfsonmicro.com; linux-kernel@vger.kernel.org
> Cc: linux-omap@vger.kernel.org; Nori, Sekhar; AnilKumar, Chimata

A pet peeve which I haven't told anyone about.  If you've cc'ed someone
on a patch then I want to cc them on the patch too.  That means I have
to add their Cc: lines to the changelog.  But such Cc: lines include
their real names.  By omitting their real names in the above fashion,
you cause extra hassle for me.  Ideally, you should add their Cc: to
the changelog as well as to the mail headers, to give thsoe people the
best chance of seeing what is happening with the patch.

>
> ..
>
> +static ssize_t lis3lv02d_range_show(struct device *dev,
> +			       struct device_attribute *attr, char *buf)
> +{
> +	lis3lv02d_sysfs_poweron(&lis3_dev);
> +	return sprintf(buf, "%d\n", lis3_dev.g_range);
> +}

Are these interfaces documented anywhere?  If so, please update that
documentation.  If not, why not ;)

> @@ -809,15 +881,33 @@ static ssize_t lis3lv02d_rate_set(struct device *dev,
>  	return count;
>  }
>  
> +static ssize_t lis3lv02d_range_set(struct device *dev,
> +				struct device_attribute *attr, const char *buf,
> +				size_t count)
> +{
> +	unsigned long range;
> +
> +	if (strict_strtoul(buf, 0, &range))

checkpatch would have told you that strict_strtoul() is deprecated. 
Please always use checkpatch.


  parent reply	other threads:[~2012-01-17 23:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1324617892-14576-1-git-send-email-anilkumar@ti.com>
2011-12-23 11:18 ` [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital Mark Brown
2011-12-28  9:14   ` AnilKumar, Chimata
2012-01-17  7:32 ` AnilKumar, Chimata
2012-01-17 10:54   ` Mark Brown
2012-01-17 16:03     ` greg
2012-01-18  5:48       ` AnilKumar, Chimata
2012-01-17 23:47   ` Andrew Morton [this message]
2012-01-18  7:51     ` AnilKumar, Chimata
2012-01-18 14:03   ` Arnd Bergmann
2012-01-18 14:43     ` Jean Delvare
2012-01-18 14:49       ` Arnd Bergmann
2012-01-18 15:00         ` Jean Delvare
2012-01-18 16:47     ` Jonathan Cameron
2012-01-18 17:11       ` Arnd Bergmann
2012-01-19  5:30         ` AnilKumar, Chimata
2012-01-19 17:10           ` Arnd Bergmann
2012-01-19 17:29             ` Mark Brown
2012-07-25  8:57             ` AnilKumar, Chimata
2012-01-18 21:36     ` Andi
2012-01-19 14:26       ` Arnd Bergmann
2012-01-19 17:15         ` Jonathan Cameron

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=20120117154702.d009df12.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=anilkumar@ti.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.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;
as well as URLs for NNTP newsgroup(s).