From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] DMA: Fix Marvell Orion and mv_xor after MEMSET removal
Date: Mon, 01 Jul 2013 17:14:25 +0200 [thread overview]
Message-ID: <51D19CD1.3030900@gmail.com> (raw)
In-Reply-To: <20130701150407.GB19937@titan.lakedaemon.net>
On 07/01/13 17:04, Jason Cooper wrote:
> On Mon, Jul 01, 2013 at 04:56:29PM +0200, Sebastian Hesselbarth wrote:
>> Commit 834cbfe966bece50afded79da8e975d255bf0772
>> ("drivers/dma: remove unused support for MEMSET operations")
>> removes MEMSET from dmaengine but does not completely removes it from
>> Marvell Orion (arch/arm/plat-orion) and XOR (drivers/dma/mv_xor).
>> This also fixes some compiler warnings about now obsolete functions by
>> removing those.
>>
>> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
>> ---
>> Cc: Jason Cooper <jason@lakedaemon.net>
>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>> Cc: Kyungmin Park <kyungmin.park@samsung.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: linux-arm-kernel at lists.infradead.org
>> Cc: linux-kernel at vger.kernel.org
>> ---
>> arch/arm/plat-orion/common.c | 6 ------
>> drivers/dma/mv_xor.c | 25 +------------------------
>> 2 files changed, 1 insertions(+), 30 deletions(-)
>
> Please take a look at the email from lkml I just forwarded to you. I
> believe this solves your problem, but I don't have time to look closely
> atm.
Jason,
I have seen the forwarded patch before. I don't know what version this
is based on. Some of the modifications are in next-20130701, some are
not. I have stripped the Marvell modifications from the patch you
forwarded and fixed all remaining issues.
Also, I will sent a follow-up patch to remove memset references from
Marvell SoC dts/dtsi and the binding documentation soon.
I guess, Bartolomiej should pick them up and resend his patch set, or
leave Marvell alone and you pick them up.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DMA: Fix Marvell Orion and mv_xor after MEMSET removal
Date: Mon, 01 Jul 2013 17:14:25 +0200 [thread overview]
Message-ID: <51D19CD1.3030900@gmail.com> (raw)
In-Reply-To: <20130701150407.GB19937@titan.lakedaemon.net>
On 07/01/13 17:04, Jason Cooper wrote:
> On Mon, Jul 01, 2013 at 04:56:29PM +0200, Sebastian Hesselbarth wrote:
>> Commit 834cbfe966bece50afded79da8e975d255bf0772
>> ("drivers/dma: remove unused support for MEMSET operations")
>> removes MEMSET from dmaengine but does not completely removes it from
>> Marvell Orion (arch/arm/plat-orion) and XOR (drivers/dma/mv_xor).
>> This also fixes some compiler warnings about now obsolete functions by
>> removing those.
>>
>> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
>> ---
>> Cc: Jason Cooper <jason@lakedaemon.net>
>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>> Cc: Kyungmin Park <kyungmin.park@samsung.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>> arch/arm/plat-orion/common.c | 6 ------
>> drivers/dma/mv_xor.c | 25 +------------------------
>> 2 files changed, 1 insertions(+), 30 deletions(-)
>
> Please take a look at the email from lkml I just forwarded to you. I
> believe this solves your problem, but I don't have time to look closely
> atm.
Jason,
I have seen the forwarded patch before. I don't know what version this
is based on. Some of the modifications are in next-20130701, some are
not. I have stripped the Marvell modifications from the patch you
forwarded and fixed all remaining issues.
Also, I will sent a follow-up patch to remove memset references from
Marvell SoC dts/dtsi and the binding documentation soon.
I guess, Bartolomiej should pick them up and resend his patch set, or
leave Marvell alone and you pick them up.
Sebastian
next prev parent reply other threads:[~2013-07-01 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 14:56 [PATCH] DMA: Fix Marvell Orion and mv_xor after MEMSET removal Sebastian Hesselbarth
2013-07-01 14:56 ` Sebastian Hesselbarth
2013-07-01 15:04 ` Jason Cooper
2013-07-01 15:04 ` Jason Cooper
2013-07-01 15:14 ` Sebastian Hesselbarth [this message]
2013-07-01 15:14 ` Sebastian Hesselbarth
2013-07-01 15:17 ` Jason Cooper
2013-07-01 15:17 ` Jason Cooper
2013-07-01 17:24 ` Bartlomiej Zolnierkiewicz
2013-07-01 17:24 ` Bartlomiej Zolnierkiewicz
2013-07-01 17:29 ` Sebastian Hesselbarth
2013-07-01 17:29 ` Sebastian Hesselbarth
2013-07-01 19:42 ` Andrew Morton
2013-07-01 19:42 ` Andrew Morton
2013-07-01 21:37 ` Jason Cooper
2013-07-01 21:37 ` Jason Cooper
2013-07-01 21:41 ` Andrew Morton
2013-07-01 21:41 ` Andrew Morton
2013-07-01 22:03 ` Sebastian Hesselbarth
2013-07-01 22:03 ` Sebastian Hesselbarth
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=51D19CD1.3030900@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.