All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@nokia.com>
Cc: "ext Nayak, Rajendra" <rnayak@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	"Hogander Jouni (Nokia-D/Tampere)" <jouni.hogander@nokia.com>,
	"V, Hemanth" <hemanthv@ti.com>
Subject: Re: [PATCH PM] OMAP3 McSPI:  Adds context save/restore
Date: Wed, 11 Feb 2009 16:34:57 -0800	[thread overview]
Message-ID: <20090212003455.GF13748@atomide.com> (raw)
In-Reply-To: <498C29E2.5020303@nokia.com>

* Aaro Koskinen <aaro.koskinen@nokia.com> [090206 04:17]:
> Hello,
>
> ext Nayak, Rajendra wrote:
>> From: Hemanth V <hemanthv@ti.com>
>>
>> This patch adds context save/restore feature to McSPI driver.
>> This includes fixes by Aaro Koskinen
>>
>> Signed-off-by: Hemanth V <hemanthv@ti.com>
>
> For some reason git-am does not take this to my tree, but when applied  
> with patch it's OK. So the patch may need to be refreshed, but for the  
> code itself:
>
> Reviewed-by: Aaro Koskinen <Aaro.Koskinen@nokia.com>

I've noted that happens when the mail is quoted-printable. One way to
deal with that is to pipe the mail to mewdecode -q > /tmp/out.patch,
then manually edit the patch to remove the quoted printable header line.

Anybody know of a better way to deal with these patches?

Tony

      reply	other threads:[~2009-02-12  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 10:20 [PATCH PM] OMAP3 McSPI: Adds context save/restore Nayak, Rajendra
2009-02-06 12:15 ` Aaro Koskinen
2009-02-12  0:34   ` Tony Lindgren [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=20090212003455.GF13748@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@nokia.com \
    --cc=hemanthv@ti.com \
    --cc=jouni.hogander@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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.