From: Greg KH <gregkh@linuxfoundation.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: stable@vger.kernel.org, Andrea Adami <andrea.adami@gmail.com>
Subject: Re: Issue with pxa_dma driver on linux 4.4.y
Date: Tue, 3 Oct 2017 10:58:18 +0200 [thread overview]
Message-ID: <20171003085818.GG15659@kroah.com> (raw)
In-Reply-To: <87ing6bgzt.fsf@belgarion.home>
On Mon, Sep 25, 2017 at 11:33:42PM +0200, Robert Jarzmik wrote:
> Dear maintainers,
>
> In the tagging of fixing commits, I have submitted this patch which was merged
> into the stable tree :
> - 6bab1c6afdca ("dmaengine: pxa_dma: fix the maximum requestor line")
> which translated into this commit in the stable tree :
> - 94d75e190f19 ("dmaengine: pxa_dma: fix the maximum requestor line")
>
> Unfortunately I have not tagged the dependant patches this one relies on, and
> more specifically :
> - build breakage fix :
> - c283e41ef324 ("dmaengine: mmp-pdma: add number of requestors")
> - functionality breakage fix :
> - 72b195cb7162 ("ARM: pxa: add the number of DMA requestor lines")
> - 4c35430ad18f ("ARM: pxa: fix the number of DMA requestor lines")
>
> I see 2 ways out of this situation :
> - either we revert stable commit 94d75e190f19
> => functionnality will remain broken, but only for a subset of DMA lines
> - or apply the dependant patches, ie. c283e41ef324, 72b195cb7162, 4c35430ad18f
>
> It's up to you, but if you could choose one and apply it, the build breakage
> will be gone.
I've applied the extra patches, thanks for letting me know.
> I must mention that there is no defconfig file so far with covers this specific
> build, and this was seen by Andrea who reported the issue.
Ah, that's why none of the build systems caught this. Perhaps we should
add a defconfig for this? Is there one in Linus's tree yet?
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-03 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:33 Issue with pxa_dma driver on linux 4.4.y Robert Jarzmik
2017-10-03 8:58 ` Greg KH [this message]
2017-10-04 8:30 ` Andrea Adami
2017-10-06 6:45 ` Robert Jarzmik
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=20171003085818.GG15659@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrea.adami@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=stable@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 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.