From: Vinod Koul <vinod.koul@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: comment in commit in the slave-dma tree (dmaengine: dw_dmac: Enhance device tree support)
Date: Tue, 8 Jan 2013 00:20:21 -0800 [thread overview]
Message-ID: <20130108082021.GD19691@intel.com> (raw)
In-Reply-To: <CAOh2x=kJjv01bFLKqnAADfnW1t64YjPwM05Xs=5XXR8yB5my1w@mail.gmail.com>
On Tue, Jan 08, 2013 at 10:19:12AM +0530, Viresh Kumar wrote:
> @Vinod: I hope you can edit this patch yourself?
Done, I have removed this and another instance
--
~Vinod
next prev parent reply other threads:[~2013-01-08 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 22:35 linux-next: comment in commit in the slave-dma tree (dmaengine: dw_dmac: Enhance device tree support) Stephen Rothwell
2013-01-07 22:43 ` Greg Kroah-Hartman
2013-01-07 22:57 ` Stephen Rothwell
2013-01-08 8:19 ` Vinod Koul
2013-01-08 4:49 ` Viresh Kumar
2013-01-08 8:20 ` Vinod Koul [this message]
2013-01-08 8:17 ` Vinod Koul
2013-01-08 11:36 ` Stephen Rothwell
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=20130108082021.GD19691@intel.com \
--to=vinod.koul@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viresh.kumar@linaro.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 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).