From: Joe Perches <joe@perches.com>
To: Kevin Tsai <ktsai@capellamicro.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Arnd Bergmann <arnd@arndb.de>, Jingoo Han <jingoohan1@gmail.com>,
Daniel Baluta <daniel.baluta@intel.com>,
Roberta Dobrescu <roberta.dobrescu@gmail.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/6] iio: light: Updated Vishay Capella cm32181 ambient light sensor driver.
Date: Thu, 21 May 2015 21:36:58 -0700 [thread overview]
Message-ID: <1432269418.29657.5.camel@perches.com> (raw)
In-Reply-To: <1432268380-7302-1-git-send-email-ktsai@capellamicro.com>
On Thu, 2015-05-21 at 21:19 -0700, Kevin Tsai wrote:
> - Renamed company name.
> - Removed cm32181_reg.
> - Removed white space.
> - Removed unused include files.
> - Updated macro definitions.
> - Renamed cm32181_chip pointer to chip.
Hi Kevin,
Please don't use the same title for multiple patches.
It'd be better if these 6 patches were titled something like
1/6 cm32181: Neatening
2/6 cm32181: Add cm32181_als_info
3/6: cm32181: Add power management support
4/6: cm32181: Add and use cm32181_als_it_scale
5/6: cm32181: Add device tree support
6/6: cm32181: Add interrupt suppor
It's
next prev parent reply other threads:[~2015-05-22 4:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 4:19 [PATCH 1/6] iio: light: Updated Vishay Capella cm32181 ambient light sensor driver Kevin Tsai
2015-05-22 4:19 ` Kevin Tsai
2015-05-22 4:19 ` [PATCH 2/6] " Kevin Tsai
2015-05-23 11:02 ` Jonathan Cameron
2015-05-22 4:19 ` [PATCH 3/6] " Kevin Tsai
2015-05-23 11:04 ` Jonathan Cameron
2015-05-23 11:04 ` Jonathan Cameron
2015-05-22 4:19 ` [PATCH 4/6] " Kevin Tsai
2015-05-23 11:10 ` Jonathan Cameron
2015-05-22 4:19 ` [PATCH 5/6] " Kevin Tsai
2015-05-23 11:15 ` Jonathan Cameron
2015-05-23 11:15 ` Jonathan Cameron
2015-05-22 4:19 ` [PATCH 6/6] " Kevin Tsai
2015-05-22 4:19 ` Kevin Tsai
2015-05-22 8:26 ` Peter Meerwald
2015-05-23 11:21 ` Jonathan Cameron
2015-05-23 11:21 ` Jonathan Cameron
2015-05-22 4:36 ` Joe Perches [this message]
2015-05-22 4:39 ` [PATCH 1/6] " Joe Perches
2015-05-23 10:57 ` Jonathan Cameron
2015-05-23 10:57 ` 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=1432269418.29657.5.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel.baluta@intel.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=knaack.h@gmx.de \
--cc=ktsai@capellamicro.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=roberta.dobrescu@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.