From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
Magnus Damm <damm@opensource.se>,
Simon Horman <horms@verge.net.au>,
Ian Molton <ian@mnementh.co.uk>
Subject: Re: [PATCH] mmc: tmio: fix PM in DMA mode
Date: Thu, 12 May 2011 18:12:35 -0400 [thread overview]
Message-ID: <m3oc37woto.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1105121212120.24486@axis700.grange> (Guennadi Liakhovetski's message of "Thu, 12 May 2011 12:19:10 +0200 (CEST)")
Hi Guennadi,
On Thu, May 12 2011, Guennadi Liakhovetski wrote:
>> > Please could you send a full patchset against mmc-next for tmio for .40?
>>
>> Can I also base my patches on next-2.6? I need both - latest mmc and pm,
>> so, using next would make it much easier.
>
> I rebased my stack on top of today's next, no changes were required, so,
> here's the order, I have the patches in my tree:
>
> https://patchwork.kernel.org/patch/711251/
> https://patchwork.kernel.org/patch/757602/
> https://patchwork.kernel.org/patch/757612/
> https://patchwork.kernel.org/patch/724081/
> https://patchwork.kernel.org/patch/761882/
> https://patchwork.kernel.org/patch/761902/
> https://patchwork.kernel.org/patch/761922/
> https://patchwork.kernel.org/patch/761942/
> https://patchwork.kernel.org/patch/777232/
> https://patchwork.kernel.org/patch/777262/
>
> As long as we manage to get these in 2.6.40 merge window early enough,
> we'll be able to push related arch patches via shmobile trees.
Thanks, all looks good to me -- pushed to mmc-next, and I'll try to
merge early in .40.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
Magnus Damm <damm@opensource.se>,
Simon Horman <horms@verge.net.au>,
Ian Molton <ian@mnementh.co.uk>
Subject: Re: [PATCH] mmc: tmio: fix PM in DMA mode
Date: Thu, 12 May 2011 22:12:35 +0000 [thread overview]
Message-ID: <m3oc37woto.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1105121212120.24486@axis700.grange> (Guennadi Liakhovetski's message of "Thu, 12 May 2011 12:19:10 +0200 (CEST)")
Hi Guennadi,
On Thu, May 12 2011, Guennadi Liakhovetski wrote:
>> > Please could you send a full patchset against mmc-next for tmio for .40?
>>
>> Can I also base my patches on next-2.6? I need both - latest mmc and pm,
>> so, using next would make it much easier.
>
> I rebased my stack on top of today's next, no changes were required, so,
> here's the order, I have the patches in my tree:
>
> https://patchwork.kernel.org/patch/711251/
> https://patchwork.kernel.org/patch/757602/
> https://patchwork.kernel.org/patch/757612/
> https://patchwork.kernel.org/patch/724081/
> https://patchwork.kernel.org/patch/761882/
> https://patchwork.kernel.org/patch/761902/
> https://patchwork.kernel.org/patch/761922/
> https://patchwork.kernel.org/patch/761942/
> https://patchwork.kernel.org/patch/777232/
> https://patchwork.kernel.org/patch/777262/
>
> As long as we manage to get these in 2.6.40 merge window early enough,
> we'll be able to push related arch patches via shmobile trees.
Thanks, all looks good to me -- pushed to mmc-next, and I'll try to
merge early in .40.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-05-12 22:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 17:11 [PATCH] mmc: tmio: fix PM in DMA mode Guennadi Liakhovetski
2011-04-29 17:11 ` Guennadi Liakhovetski
2011-05-11 1:20 ` Chris Ball
2011-05-11 1:20 ` Chris Ball
2011-05-12 8:17 ` Guennadi Liakhovetski
2011-05-12 8:17 ` Guennadi Liakhovetski
2011-05-12 10:19 ` Guennadi Liakhovetski
2011-05-12 10:19 ` Guennadi Liakhovetski
2011-05-12 22:12 ` Chris Ball [this message]
2011-05-12 22:12 ` Chris Ball
2011-05-26 1:24 ` Chris Ball
2011-05-26 1:24 ` Chris Ball
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=m3oc37woto.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@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 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.