From: Viresh Kumar <viresh.kumar@st.com>
To: Dan <dan.j.williams@intel.com>, Vinod Koul <vinod.koul@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Armando VISCONTI <armando.visconti@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Vipin KUMAR <vipin.kumar@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Deepak SIKRI <deepak.sikri@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Amit VIRDI <Amit.VIRDI@st.com>,
Pratyush ANAND <pratyush.anand@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>,
"viresh.linux@gmail.com" <viresh.linux@gmail.com>,
Bhavna YADAV <bhavna.yadav@st.com>
Subject: Re: [PATCH 1/3] dmaengine: Allow controller drivers to set channel ids
Date: Wed, 16 Nov 2011 17:11:20 +0530 [thread overview]
Message-ID: <4EC3A160.8050608@st.com> (raw)
In-Reply-To: <4EAE76CB.3070508@st.com>
On 10/31/2011 3:52 PM, Viresh Kumar wrote:
> On 10/14/2011 11:13 AM, Vinod Koul wrote:
>>>> >> > Hi Vinod/Dan,
>>>> >> >
>>>> >> > Any update/feedback on this?
>> > Since this touches non slave stuff as well, I need Dan to ack it first
> Hi Dan,
>
> Can you please provide some comments on this.
Vinod,
It looks Dan has missed this patchset somehow. :(
Can you please get his views about this patchset, if possible.
--
viresh
next prev parent reply other threads:[~2011-11-16 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 10:43 Viresh Kumar
2011-09-22 10:43 ` [PATCH 2/3] dmaengine/dw_dmac: Set channel id's in controller driver Viresh Kumar
2011-09-22 10:43 ` [PATCH 3/3] dmaengine/dw_dmac: Don't use magic number for total number of channels Viresh Kumar
2011-09-28 9:08 ` [PATCH 1/3] dmaengine: Allow controller drivers to set channel ids Vinod Koul
2011-10-13 8:46 ` Viresh Kumar
2011-10-14 5:43 ` Vinod Koul
2011-10-31 10:22 ` Viresh Kumar
2011-11-16 11:41 ` Viresh Kumar [this message]
2011-11-28 4:05 ` Viresh Kumar
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=4EC3A160.8050608@st.com \
--to=viresh.kumar@st.com \
--cc=Amit.VIRDI@st.com \
--cc=armando.visconti@st.com \
--cc=bhavna.yadav@st.com \
--cc=bhupesh.sharma@st.com \
--cc=dan.j.williams@intel.com \
--cc=deepak.sikri@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pratyush.anand@st.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=vinod.koul@intel.com \
--cc=vipin.kumar@st.com \
--cc=vipulkumar.samar@st.com \
--cc=viresh.linux@gmail.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
Powered by JetHome