From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:60238 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751199AbcKOT1O (ORCPT
        <rfc822;stable@vger.kernel.org>); Tue, 15 Nov 2016 14:27:14 -0500
Date: Tue, 15 Nov 2016 20:27:23 +0100
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
Message-ID: <20161115192723.GA7094@kroah.com>
References: <20161115153048.5424-1-nicolas.ferre@atmel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161115153048.5424-1-nicolas.ferre@atmel.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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