From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, gregkh <gregkh@linuxfoundation.org>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Tom Gall <tom.gall@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
Vinod Koul <vinod.koul@intel.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dmaengine@vger.kernel.org
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: Mon, 12 Jun 2017 15:33:40 +0200 [thread overview]
Message-ID: <1497274420.11261.8.camel@Nokia-N900> (raw)
In-Reply-To: <CAK8P3a38TN5ZKL4j_xHtkQYV1NGrg28To4HW_FCfJy882kNCfg@mail.gmail.com>
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.
prev parent reply other threads:[~2017-06-12 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <593e7405.13d31c0a.ae58e.4696@mx.google.com>
2017-06-12 11:28 ` stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed, 13 errors, 4 warnings (v4.4.71-63-g409ebd600970) Arnd Bergmann
2017-06-12 11:28 ` Arnd Bergmann
2017-06-12 11:59 ` gregkh
2017-06-12 12:44 ` Arnd Bergmann
2017-06-12 13:33 ` Alexander Sverdlin [this message]
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=1497274420.11261.8.camel@Nokia-N900 \
--to=alexander.sverdlin@gmail.com \
--cc=amit.pundir@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.org \
--cc=vinod.koul@intel.com \
/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