linux-kernel - Re: [PATCH v2 2/2] dmaengine: dw: Remove AVR32 bits from the driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1494841350.6967.55.camel@linux.intel.com>
Date:   Mon, 15 May 2017 12:42:30 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Lars-Peter Clausen <lars@...afoo.de>,
        Vinod Koul <vinod.koul@...el.com>
Cc:     Hans-Christian Noren Egtvedt <egtvedt@...fundet.no>,
        linux-kernel@...r.kernel.org,
        Haavard Skinnemoen <hskinnemoen@...il.com>,
        Nicolas Ferre <nicolas.ferre@...el.com>,
        Boris Brezillon <boris.brezillon@...e-electrons.com>,
        Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        alsa-devel@...a-project.org, dmaengine@...r.kernel.org,
        Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>
Subject: Re: [PATCH v2 2/2] dmaengine: dw: Remove AVR32 bits from the driver

On Mon, 2017-05-15 at 11:25 +0200, Lars-Peter Clausen wrote:
> On 05/15/2017 10:43 AM, Andy Shevchenko wrote:
> > On Sun, 2017-05-14 at 18:34 +0530, Vinod Koul wrote:
> > > On Tue, May 09, 2017 at 07:18:37PM +0300, Andy Shevchenko wrote:
> > > > AVR32 is gone. Now it's time to clean up the driver by removing
> > > > leftovers that was used by AVR32 related code.
> > > 
> > > Since the cover didn't mention any dependency, I went ahead and
> > > applied this
> > > now
> > > 
> > 
> > Sorry, I forgot to mention that it's supposed to go via either tree,
> > though together. Since first we remove users of non-standard DMA
> > callbacks.
> > 
> 
> Since there is no hurry maybe split it over multiple releases. Audio
> patch
> now through the audio tree and once it has made it to a upstream
> release
> apply the DMA patch through the DMA tree.

While there is indeed no hurry (I'm not expecting long patches against
dw_dmac), we may do that, though OTOH better to do it at once to
minimize a probability that the second change might be forgotten for
longer.

-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy