From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 437E2C48BD5 for ; Tue, 25 Jun 2019 15:46:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 158B9208E3 for ; Tue, 25 Jun 2019 15:46:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="qXtq11Gc" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731241AbfFYPqI (ORCPT ); Tue, 25 Jun 2019 11:46:08 -0400 Received: from mail-lf1-f65.google.com ([209.85.167.65]:44487 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727572AbfFYPqI (ORCPT ); Tue, 25 Jun 2019 11:46:08 -0400 Received: by mail-lf1-f65.google.com with SMTP id r15so12950443lfm.11; Tue, 25 Jun 2019 08:46:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5HkYvt7vqYcoplSqjUO7R3ulPIH/lqglCxToVLLxHq0=; b=qXtq11GckrDcJCHDDEgthhpG8mHYmTpXpzctewOXeUwZmzUo0b5ZeAtMwVAfPHhIPT 3RhfwsBrNQETw2uzvpCbSc8dG/ITMshgLL9OzsWB5XOnH1VuBhB1eJF709b3TLytZa66 iPZ6oUBRjQ47hp3xXYtwKt8NpfCcGF3sPAHVG6KRSOSsrYYx/5qUxulw8KdpvUSSNZ6j wxuwby4vZz9pG3VaHAkPbhhkzSoLLFtCq/7AA0gftSopUeZpN5J3cYWU7xqUlQBj2TsE sWo6eQY/SLn3t/XWBGW9SmsuLqBCzeFuVIqOzL9A+qq68NVNOowGczMSJrmpmUYAm2p8 RLHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5HkYvt7vqYcoplSqjUO7R3ulPIH/lqglCxToVLLxHq0=; b=RImzWAmk85hJDcS1JoVRUHJZsED/dm/ANwRrs0ZmC3wQwRNkrX5kzi+3zNSW+Ym3fY 2TabmsQABekY508UA6/WlZACtnDjHsVfgnYlyh7JlPI+kQAdqlfM2aCcPACQfUM4NCO3 lPBWYfIjaRZbrBEzPePaddb+n1JpZKuwhxTJ8uGy0N5kWY4Nj1krJcwTcyEQZbWqxlqL 6gm8sXToCbozozXxsUuNDrcBxt2+IytEF6Uepm5HoDURNqhmy973Dx2+heZ8MeQvzB4N QDfE/DVUjiP3w2b+lSEZBb/1BFmutYJDFt3RfsoVnTMlsQhv9injIw25YmUvbno9sb0y t+Ew== X-Gm-Message-State: APjAAAUvHn6RMLmycI9CtS0Y+fw8se2C4p1BFcyj/0CY2lTpAJ9++X+A qPx+7ArbDpYx6lz/lMfImfP7hIYHc0LD3WOJ4UA= X-Google-Smtp-Source: APXvYqzVkv3ISEpy81fk9GqWVELv6LncGBQA618cty6rXyn6Ym+TyTksnqIcZ4ZJkwyOgbRhI2GPWbZy/JzI4c4/Nq0= X-Received: by 2002:ac2:5a5e:: with SMTP id r30mr16968201lfn.12.1561477566289; Tue, 25 Jun 2019 08:46:06 -0700 (PDT) MIME-Version: 1.0 References: <20190621082306.34415-1-yibin.gong@nxp.com> In-Reply-To: From: Fabio Estevam Date: Tue, 25 Jun 2019 12:45:54 -0300 Message-ID: Subject: Re: [PATCH v2] dmaengine: imx-sdma: remove BD_INTR for channel0 To: Robin Gong Cc: Shawn Guo , Sascha Hauer , Vinod , Dan Williams , Sven Van Asbroeck , Michael Olbrich , dl-linux-imx , stable , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "dmaengine@vger.kernel.org" , Sascha Hauer Content-Type: text/plain; charset="UTF-8" Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org Hi Robin, On Tue, Jun 25, 2019 at 4:36 AM Robin Gong wrote: > Yes, although Sven only met this issue after v4.19, this potential issue should be there. > But 1d069bfa3c78 seems merged from v4.7 instead? Yes, you could simply do: Fixes: 1d069bfa3c78 ("dmaengine: imx-sdma: ack channel 0 IRQ in the interrupt handler") Cc: stable@vger.kernel.org And it will get applied to all relevant stable trees. Thanks