From: Vinod Koul <vinod.koul@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Zhang Wei <zw@melbourneit.hotkeysparking.com>,
Dan Williams <djbw@fb.com>,
linux-tegra@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/12] dma: various minor clean ups for slave drivers
Date: Mon, 15 Jul 2013 15:29:42 +0530 [thread overview]
Message-ID: <20130715095942.GQ16653@intel.com> (raw)
In-Reply-To: <1373883677.24799.243.camel@smile>
On Mon, Jul 15, 2013 at 01:21:17PM +0300, Andy Shevchenko wrote:
> On Mon, 2013-07-15 at 15:07 +0530, Vinod Koul wrote:
> > On Thu, May 30, 2013 at 09:32:19PM +0300, Andy Shevchenko wrote:
> > > >> Here is a set of small independent patches that clean up or fix minor things
> > > >> across DMA slave drivers.
> >
> > Applied thanks
>
> Thank you. You were faster than me, I was just about to send rebased
> version.
:)
I suspected changes are trivial and it should apply or with slight modfications.
it did apply cleanly so no reason to delay applying on shiny new -rc1
For folks in this part of world, monday morning Linus drops the rc1 usually, so
get staright to it!
--
~Vinod
next prev parent reply other threads:[~2013-07-15 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 12:14 [PATCH 00/12] dma: various minor clean ups for slave drivers Andy Shevchenko
2013-05-27 12:14 ` [PATCH 05/12] fsldma: remove useless use of lock Andy Shevchenko
2013-05-30 17:47 ` [PATCH 00/12] dma: various minor clean ups for slave drivers Vinod Koul
2013-05-30 18:32 ` Andy Shevchenko
2013-07-15 9:37 ` Vinod Koul
2013-07-15 10:21 ` Andy Shevchenko
2013-07-15 9:59 ` Vinod Koul [this message]
2013-06-01 0:09 ` Dan Williams
2013-07-15 9:33 ` Vinod Koul
2013-07-10 7:54 ` Andy Shevchenko
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=20130715095942.GQ16653@intel.com \
--to=vinod.koul@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=zw@melbourneit.hotkeysparking.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).