Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1663512

Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed, 13 errors, 4 warnings (v4.4.71-63-g409ebd600970)

From Alexander Sverdlin <alexander.sverdlin@gmail.com>
Newsgroups linux.kernel
Subject Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed, 13 errors, 4 warnings (v4.4.71-63-g409ebd600970)
Date 2017-06-12 15:40 +0200
Message-ID <tRxJv-2GO-13@gated-at.bofh.it> (permalink)
References <tRvHH-1ua-11@gated-at.bofh.it> <tRvHH-1ua-9@gated-at.bofh.it> <tRvHH-1ua-13@gated-at.bofh.it> <tRwkp-1VP-5@gated-at.bofh.it> <tRwX7-2bL-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hello!

On Mon Jun 12 14:44:04 2017 Arnd Bergmann <arnd@arndb.de> wrote:
> On Mon, Jun 12, 2017 at 1:59 PM, gregkh <gregkh@linuxfoundation.org>
> wrote:
> > On Mon, Jun 12, 2017 at 01:28:48PM +0200, Arnd Bergmann wrote:
> > > > > 1   drivers/dma/ep93xx_dma.c:1357:9: error: 'struct dma_device'
> > > > > has no member named 'device_synchronize'
> > > > 
> > > > The error was introudced by the backport of 98f9de366fcc
> > > > ("dmaengine: ep93xx: Don't drain the transfers in
> > > > terminate_all()"), which requires the dmaengine synchronize
> > > > callback.
> > > > 
> > > > device_synchronize was introduced by b36f09c3c441 ("dmaengine: Add
> > > > transfer termination synchronization support") in linux-4.5. That
> > > > is not a bugfix but would
> > > > cleanly apply on top of 4.4 and has no dependencies or
> > > > side-effects.
> > > > 
> > > > We can either revert 98f9de366fcc or backport b36f09c3c441.
> > 
> > I'll just go drop 98f9de366fcc as that's best here.   I don't think
> > anyone really cares about this driver in 4.4, and if they do, then they
> > can speak up :)
> 
> Sounds fine. ep93xx was once an important platform and the chips are
> still being sold, but I guess not many users remain. Alexander Sverdlin
> just stepped up as the platform maintainer, so he can decide whether he
> wants his fix in linux-4.4.y.

Fair enough! While I'm aware of several thousands devices still in service, there is no "enterprise Linux distribution" for this platform, these embedded devices are able to switch to the fresh kernel.

So, it doesn't worth the effort, repairing v4.4.x is meaningless.

--
Thanks,
Alexander.

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed,  13 errors, 4 warnings (v4.4.71-63-g409ebd600970) Arnd Bergmann <arnd@arndb.de> - 2017-06-12 13:30 +0200
  Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed,  13 errors, 4 warnings (v4.4.71-63-g409ebd600970) Arnd Bergmann <arnd@arndb.de> - 2017-06-12 13:30 +0200
    Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed,  13 errors, 4 warnings (v4.4.71-63-g409ebd600970) gregkh <gregkh@linuxfoundation.org> - 2017-06-12 14:10 +0200
      Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed,  13 errors, 4 warnings (v4.4.71-63-g409ebd600970) Arnd Bergmann <arnd@arndb.de> - 2017-06-12 14:50 +0200
        Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186         passed, 13 errors, 4 warnings (v4.4.71-63-g409ebd600970) Alexander Sverdlin <alexander.sverdlin@gmail.com> - 2017-06-12 15:40 +0200

csiph-web