From: Per Forlin <per.forlin@linaro.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Per Forlin <per.forlin@stericsson.com>,
linux-kernel@vger.kernel.org, "Koul,
Vinod" <vinod.koul@intel.com>
Subject: Re: [PATCH] ste_dma40: assign device_prep_dma_sg for dma_memcpy
Date: Sun, 13 Mar 2011 21:20:41 +0100 [thread overview]
Message-ID: <AANLkTim59WW+cruLM7DN5aMgY_mLB+YEB83tU-sxgu4N@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinPHzHBGNtOmV_Ze9whbN8zNN0+Z0oge-DwFCbu@mail.gmail.com>
On 11 March 2011 23:52, Dan Williams <dan.j.williams@intel.com> wrote:
> On Wed, Mar 2, 2011 at 4:42 PM, Koul, Vinod <vinod.koul@intel.com> wrote:
>> On Tue, 2011-03-01 at 11:32 +0100, Per Forlin wrote:
>>> From: Per Forlin <per.forlin@linaro.org>
>>>
>>> Signed-off-by: Per Forlin <per.forlin@linaro.org>
>>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>> ---
>>> drivers/dma/ste_dma40.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
>>> index 6e1d46a..1dd8ea3 100644
>>> --- a/drivers/dma/ste_dma40.c
>>> +++ b/drivers/dma/ste_dma40.c
>>> @@ -2496,7 +2496,7 @@ static int __init d40_dmaengine_init(struct d40_base *base,
>>> base->dma_memcpy.device_alloc_chan_resources = d40_alloc_chan_resources;
>>> base->dma_memcpy.device_free_chan_resources = d40_free_chan_resources;
>>> base->dma_memcpy.device_prep_dma_memcpy = d40_prep_memcpy;
>>> - base->dma_slave.device_prep_dma_sg = d40_prep_sg;
>>> + base->dma_memcpy.device_prep_dma_sg = d40_prep_sg;
>>> base->dma_memcpy.device_prep_slave_sg = d40_prep_slave_sg;
>>> base->dma_memcpy.device_tx_status = d40_tx_status;
>>> base->dma_memcpy.device_issue_pending = d40_issue_pending;
>>
>> Please copy the MAINTAINERS, or your patches can get missed...
>>
>> Applied, Thanks
>>
>
> While preparing the 2.6.39 tree this patch no longer applies, it looks
> like it is not needed after the pending conversion patches from Rabin.
> Ok to drop, or was this urgent for 2.6.38-final? If the latter the
> changelog did not indicate.
It is not urgent for 2.6.38-final, please drop it.
Thanks
Per
prev parent reply other threads:[~2011-03-13 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 10:32 Per Forlin
2011-03-03 0:42 ` Koul, Vinod
2011-03-11 22:52 ` Dan Williams
2011-03-13 20:20 ` Per Forlin [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=AANLkTim59WW+cruLM7DN5aMgY_mLB+YEB83tU-sxgu4N@mail.gmail.com \
--to=per.forlin@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®