netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: David Miller <davem@davemloft.net>
Cc: Alberto Panizzo <maramaopercheseimorto@gmail.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: smc911x: convert pxa dma to dmaengine
Date: Fri, 05 Feb 2016 22:44:56 +0100	[thread overview]
Message-ID: <87k2mi4ysn.fsf@belgarion.home> (raw)
In-Reply-To: <87fuzjl69l.fsf@belgarion.home> (Robert Jarzmik's message of "Thu, 03 Dec 2015 19:46:30 +0100")

Robert Jarzmik <robert.jarzmik@free.fr> writes:

> David Miller <davem@davemloft.net> writes:
>
>> From: Robert Jarzmik <robert.jarzmik@free.fr>
>> Date: Mon, 30 Nov 2015 22:40:28 +0100
>>
>>> Convert the dma transfers to be dmaengine based, now pxa has a dmaengine
>>> slave driver. This makes this driver a bit more PXA agnostic.
>>> 
>>> The driver was only compile tested. The risk is quite small as no
>>> current PXA platform I'm aware of is using smc911x driver.
>>> 
>>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>>
>> I've marked this 'deferred' in patchwork until someone tests
>> these changes and says they should be good on all platforms
>> this chip is used.
>
> Okay, so would any maintainer of non pxa boards give a feedback for this patch ?
> The ones I have found are :
>  - sh2007: Guennadi and Hitoshi
>  - armadillo5x0: Alberto
>  - imx v6 and imx v7: Fabio
> I've added the patch at the end of this mail for easier handling.
>
> Now, if no maintainer gives it a test, what do we do, David ? I'm intending to
> remove "arch/arm/mach-pxa/include/mach/dma.h" in the near future, which will
> break this driver somehow (at least for PXA boards, even if none is identified
> so far).
> So could we agree on a deadline, and what you wish to do : either drop the patch
> or apply, or something else.

Hi David,

Apart from Alberto who answered he cannot test it by lack of hardware, the
others didn't answer.

So how can I move forward ? Would you want me to amend the KConfig to add a "&&
!ARCH_PXA" on the "depend" line ?

Cheers.

-- 
Robert

  reply	other threads:[~2016-02-05 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 21:40 [PATCH] net: smc911x: convert pxa dma to dmaengine Robert Jarzmik
2015-12-03  4:52 ` David Miller
2015-12-03 18:46   ` Robert Jarzmik
2016-02-05 21:44     ` Robert Jarzmik [this message]
2016-02-05 22:30       ` David Miller
2016-02-06  9:05         ` Robert Jarzmik
2016-02-20 13:29           ` Hitoshi Mitake
2016-02-20 15:46             ` Guennadi Liakhovetski
     [not found]           ` <CAE1WaKK2DqYYOTLmprbLuZVN-8--sZVyZVHgkcT4Jg7797S7HQ@mail.gmail.com>
2016-02-20 14:48             ` Robert Jarzmik
2016-02-23 18:15               ` Fabio Estevam
2016-03-03 20:16                 ` Robert Jarzmik
2016-03-15 22:56                   ` Robert Jarzmik
2016-03-16  2:57                     ` David Miller

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=87k2mi4ysn.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=davem@davemloft.net \
    --cc=fabio.estevam@freescale.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maramaopercheseimorto@gmail.com \
    --cc=mitake@dcl.info.waseda.ac.jp \
    --cc=netdev@vger.kernel.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).