From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: stable@vger.kernel.org, Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [PATCH backport 4.4.y-4.8.z] dmaengine: at_xdmac: fix spurious flag status for mem2mem transfers
Date: Tue, 15 Nov 2016 20:27:23 +0100 [thread overview]
Message-ID: <20161115192723.GA7094@kroah.com> (raw)
In-Reply-To: <20161115153048.5424-1-nicolas.ferre@atmel.com>
On Tue, Nov 15, 2016 at 04:30:48PM +0100, Nicolas Ferre wrote:
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> commit 95da0c19d164f6df0b71a5187950f47d4b746e91 upstream.
>
> When setting the channel configuration register, the perid field is not
> set to 0 since it is useless for mem2mem transfers. Unfortunately, a
> device has 0 as perid. It could cause spurious flags status because
> the controller could mix some events from the two channels.
> For that reason, use the highest perid value for mem2mem transfers since it
> doesn't match the perid of other devices.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> [nicolas.ferre@atmel.com: backport to 4.4.y stable kernel]
Why does your subject say 4.4.y-4.8.y when this patch showed up in
4.5-rc1?
confused,
greg k-h
next prev parent reply other threads:[~2016-11-15 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 15:30 [PATCH backport 4.4.y-4.8.z] dmaengine: at_xdmac: fix spurious flag status for mem2mem transfers Nicolas Ferre
2016-11-15 19:27 ` Greg Kroah-Hartman [this message]
2016-11-16 8:44 ` Nicolas Ferre
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=20161115192723.GA7094@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--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 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).