From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
박경민 <kyungmin.park@samsung.com>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>,
최찬우 <cw00.choi@samsung.com>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Subject: Re: Re: [PATCH] Extcon: Arizona: Add driver for Wolfson Arizona class devices
Date: Tue, 3 Jul 2012 10:40:29 +0100 [thread overview]
Message-ID: <20120703094029.GC29030@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4681354.107331341300035007.JavaMail.weblogic@epml05>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Tue, Jul 03, 2012 at 07:20:38AM +0000, MyungJoo Ham wrote:
You should fix your mailer to word wrap within paragraphs, I've reflowed
your text for legibility.
> Though extcon-arizona.c itself does not seem to have problems, when I
> add the patches from your repository
> (http://git.kernel.org/?p=linux/kernel/git/broonie/misc.git;a=commit;h=3afbac957e3c59037a4ecaf19d68f6c8104299fc),
Please provide human readable descriptions of things!
> I get compiler errors if MFD_ARIZONA is enabled in order to enable
> EXTCON_ARIZONA. (No other Arizona-related devices are enabled; I don't
> have any of them anyway) This is not an issue w/ extcon-arizona.c, but
> I just wanted to let you know.
Note the cover letter for the series...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-03 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 7:20 Re: [PATCH] Extcon: Arizona: Add driver for Wolfson Arizona class devices MyungJoo Ham
2012-07-03 9:40 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 4:37 MyungJoo Ham
2012-07-03 19:37 ` 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=20120703094029.GC29030@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.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.