From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-omap <linux-omap@vger.kernel.org>,
spi-devel-general <spi-devel-general@lists.sourceforge.net>,
David Brownell <dbrownell@users.sourceforge.net>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH v6 1/1] OMAP2: Spi: Force CS to be in inactive state after off-mode transition
Date: Wed, 29 Dec 2010 12:07:08 +0100 [thread overview]
Message-ID: <4D1B165C.3020008@free-electrons.com> (raw)
In-Reply-To: <4D1AF8D7.6060904@free-electrons.com>
On 12/29/2010 10:01 AM, Gregory CLEMENT wrote:
>> Hi Gregory,
>>
> Hi Grant,
>
>> Patch does not apply, but I cannot immediately isolate the damage.
>> Please see if you can figure out the issue on your end. Is it your
>> mailer? I could fudge it, but in the long run it is better if this
>> issue can get sorted out now.
>>
>
> I found the problem: see below in the patch itself.
>
Indeed it was may mailer which had broken the patch. I use
git-format-patch and git imap send to create the mail. But when I
open it from the draft folder to add the email address, it decides
by itself to remove an end of line!
It is not the first time that I have some problems with Thunderbird.
I consider changing my mailer to a more "hacker friendly" one.
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-12-29 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 12:21 [PATCH v6 1/1] OMAP2: Spi: Force CS to be in inactive state after off-mode transition Gregory CLEMENT
2010-12-29 7:28 ` Grant Likely
2010-12-29 9:01 ` Gregory CLEMENT
2010-12-29 11:07 ` Gregory CLEMENT [this message]
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=4D1B165C.3020008@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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