[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinPHzHBGNtOmV_Ze9whbN8zNN0+Z0oge-DwFCbu@mail.gmail.com>
Date: Fri, 11 Mar 2011 14:52:49 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Per Forlin <per.forlin@...aro.org>,
Linus Walleij <linus.walleij@...ricsson.com>
Cc: Per Forlin <per.forlin@...ricsson.com>,
linux-kernel@...r.kernel.org, "Koul, Vinod" <vinod.koul@...el.com>
Subject: Re: [PATCH] ste_dma40: assign device_prep_dma_sg for dma_memcpy
On Wed, Mar 2, 2011 at 4:42 PM, Koul, Vinod <vinod.koul@...el.com> wrote:
> On Tue, 2011-03-01 at 11:32 +0100, Per Forlin wrote:
>> From: Per Forlin <per.forlin@...aro.org>
>>
>> Signed-off-by: Per Forlin <per.forlin@...aro.org>
>> Acked-by: Linus Walleij <linus.walleij@...aro.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.
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists