From: Kevin Hilman <khilman@deeprootsystems.com>
To: Wang Sawsd-A24013 <cqwang@motorola.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] Support OMAP3 VC adaptation with different Power IC
Date: Thu, 25 Jun 2009 10:38:50 -0700 [thread overview]
Message-ID: <871vp8qklx.fsf@deeprootsystems.com> (raw)
In-Reply-To: <B00E06E2766C2744B022DE9BAF3C59D546577C@zmy16exm69.ds.mot.com> (Wang Sawsd-A's message of "Thu\, 25 Jun 2009 00\:10\:51 +0800")
"Wang Sawsd-A24013" <cqwang@motorola.com> writes:
>> -----Original Message-----
>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>> Sent: 2009年6月24日 8:19
>> To: Wang Sawsd-A24013
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: [PATCH 1/2] Support OMAP3 VC adaptation with
>> different Power IC
>>
>> "Wang Sawsd-A24013" <cqwang@motorola.com> writes:
>>
>> > From c1aba8ba7af3ddd16346d95795bda71e65baa4d0 Mon Sep 17
>> 00:00:00 2001
>> > From: Chunqiu Wang <cqwang@motorola.com>
>> > Date: Wed, 24 Jun 2009 06:48:52 +0800
>> > Subject: [PATCH] Support OMAP3 VC adaptation with different Power IC
>> >
>> > Current OMAP SmartReflex driver only supports TI Triton
>> > Power IC, add a callback to make it possible to use
>> > different PowerIC and use different settings to
>> > configure OMAP3 Voltage Controller for DVFS
>> >
>> > Board file can setup a new function to have different settings
>> > on SR to configure their Power IC for voltage scaling
>> >
>> > Signed-off-by: Chunqiu Wang <cqwang@motorola.com>
>>
>> Your patch seems wrapped again:
>>
>> checkpatch reports:
>>
>> ERROR: patch seems to be corrupt (line wrapped?)
>> #38: FILE: arch/arm/mach-omap2/smartreflex.c:57:
>> u32 value)
>>
>> ERROR: trailing whitespace
>> #95: FILE: arch/arm/mach-omap2/smartreflex.h:252:
>> +^I^I^I^I^I^Iu8 t_vsel, u8 c_vsel); $
>>
>> total: 2 errors, 0 warnings, 71 lines checked
>>
> Sorry about that, this time I attached these two patch files.
>
Can you please fix your mailer setup so you can resend patches inline
and get a broader review.
I suggest bypassing any mailer such as outlook and configuring
git-send-email to send them directly to an SMTP server. If your local
SMTP is really that broken to be wrapping text, I suggest you
send via a gmail account. This link describes how to set this
up for gmail, but also works for a local SMTP server.
http://git.or.cz/gitwiki/GitTips#Mail
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-25 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 0:15 [PATCH 1/2] Support OMAP3 VC adaptation with different Power IC Wang Sawsd-A24013
2009-06-24 0:19 ` Kevin Hilman
2009-06-24 16:10 ` Wang Sawsd-A24013
2009-06-25 17:38 ` Kevin Hilman [this message]
2009-06-25 20:10 ` Wang Sawsd-A24013
2009-06-25 1:25 ` Mike Chan
2009-06-25 16:00 ` Wang Sawsd-A24013
2009-06-25 19:25 ` Mike Chan
2009-06-25 20:12 ` Wang Sawsd-A24013
2009-06-25 21:18 ` Mike Chan
-- strict thread matches above, loose matches on Subject: below --
2009-06-25 23:55 sawsd wang
2009-06-26 14:57 ` Kevin Hilman
2009-09-30 18:57 ` Kevin Hilman
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=871vp8qklx.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cqwang@motorola.com \
--cc=linux-omap@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