From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: ashishj3 <ashish.jangam@kpitcummins.com>
Cc: sameo@openedhand.com, linux-kernel@vger.kernel.org,
Dajun <dajun.chen@diasemi.com>,
linaro-dev@lists.linaro.org, arnd@arndb.de, eric.miao@linaro.org,
sameo@linux.intel.com
Subject: Re: [PATCH 01/11] MFD: DA9052/53 MFD core module v8
Date: Tue, 1 Nov 2011 13:02:49 +0000 [thread overview]
Message-ID: <20111101130249.GE10029@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1320152142.4892.4.camel@L-0761.kpit.com>
On Tue, Nov 01, 2011 at 06:25:42PM +0530, ashishj3 wrote:
> include/linux/mfd/da9052/reg.h | 777
> +++++++++++++++++++++++++++++++++++++
Your mail is word wrapped...
> +config PMIC_DA9052
> + bool
> + select MFD_CORE
...and all the indentation is broken.
next prev parent reply other threads:[~2011-11-01 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 12:55 [PATCH 01/11] MFD: DA9052/53 MFD core module v8 ashishj3
2011-11-01 13:02 ` Mark Brown [this message]
2011-12-05 6:46 ` ashishj3
2011-12-05 15:27 ` Mark Brown
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=20111101130249.GE10029@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=ashish.jangam@kpitcummins.com \
--cc=dajun.chen@diasemi.com \
--cc=eric.miao@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=sameo@openedhand.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