From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
To: Andrew Bresticker <abrestic@chromium.org>,
Naidu Tellapati <Naidu.Tellapati@imgtec.com>
Cc: "wim@iguana.be" <wim@iguana.be>,
"linux@roeck-us.net" <linux@roeck-us.net>,
James Hartley <James.Hartley@imgtec.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Jude Abraham <Jude.Abraham@imgtec.com>
Subject: Re: [PATCH v3 1/2] watchdog: ImgTec PDC Watchdog Timer Driver
Date: Wed, 19 Nov 2014 16:27:08 -0300 [thread overview]
Message-ID: <546CEF0C.1090204@imgtec.com> (raw)
In-Reply-To: <CAL1qeaGgs0CrWdUV8kYVxbJ-=46+Xhx__pZy390iX0OXTF1bHw@mail.gmail.com>
On 11/18/2014 08:12 PM, Andrew Bresticker wrote:
> Naidu,
>
> On Tue, Nov 18, 2014 at 4:07 AM, <Naidu.Tellapati@imgtec.com> wrote:
>> From: Naidu Tellapati <Naidu.Tellapati@imgtec.com>
>>
>> This commit adds support for ImgTec PowerDown Controller Watchdog Timer.
>>
>> Signed-off-by: Jude Abraham <Jude.Abraham@imgtec.com>
>> Signed-off-by: Naidu Tellapati <Naidu.Tellapati@imgtec.com>
>
> checkpatch reports that there's trailing whitespace and that you're
> using DOS line endings. Please be sure to fix that with this and your
> other patches.
>
Andrew,
Saving this patch with mutt as mbox and running checkpatch on it,
doesn't report any problems with it.
Maybe it's your client?
--
Ezequiel
next prev parent reply other threads:[~2014-11-19 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 12:07 [PATCH v3 0/2] watchdog: Add support for ImgTec PowerDown Controller Watchdog Timer Naidu.Tellapati
2014-11-18 12:07 ` [PATCH v3 1/2] watchdog: ImgTec PDC Watchdog Timer Driver Naidu.Tellapati
2014-11-18 23:06 ` Andrew Bresticker
2014-11-18 23:12 ` Andrew Bresticker
2014-11-19 19:27 ` Ezequiel Garcia [this message]
2014-11-19 19:35 ` Andrew Bresticker
2014-11-19 19:41 ` Naidu Tellapati
2014-11-18 12:07 ` [PATCH v3 2/2] DT: watchdog: Add ImgTec PDC Watchdog Timer binding documentation Naidu.Tellapati
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=546CEF0C.1090204@imgtec.com \
--to=ezequiel.garcia@imgtec.com \
--cc=James.Hartley@imgtec.com \
--cc=Jude.Abraham@imgtec.com \
--cc=Naidu.Tellapati@imgtec.com \
--cc=abrestic@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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