linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@ginzinger.com>
To: Sasha Levin <sashal@kernel.org>, <han.xu@nxp.com>,
	<bbrezillon@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem
Date: Fri, 8 Feb 2019 11:49:52 +0100	[thread overview]
Message-ID: <1c16de8a-fed3-c7eb-b9c4-ceccae3d915d@ginzinger.com> (raw)
In-Reply-To: <20190207163215.9174B2190A@mail.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

Hi Sasha,

On 07.02.19 17:32, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 6f2a6a52560a mtd: nand: gpmi: reset BCH earlier, too, to avoid NAND startup problems.
> 
> The bot has tested the following trees: v4.20.6, v4.19.19, v4.14.97, v4.9.154, v4.4.172, v3.18.133.
> 
> v4.20.6: Build OK!
> v4.19.19: Build OK!
> v4.14.97: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.9.154: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.4.172: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v3.18.133: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> 
> How should we proceed with this patch?

The directory structure has changed since and I've sent the backported
commit, see https://lkml.org/lkml/2019/2/8/200

That should apply to 4.14 and older stable trees.

In case you need that in a different form, please just tell me.

thanks

                               martin

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3616 bytes --]

      parent reply	other threads:[~2019-02-08 10:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 15:52 [PATCH v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem Martin Kepplinger
2019-02-05 16:28 ` Han Xu
2019-02-06  8:35 ` [v2] " Boris Brezillon
2019-02-06  8:42 ` [PATCH v2] " Boris Brezillon
     [not found] ` <20190207163215.9174B2190A@mail.kernel.org>
2019-02-08 10:49   ` Martin Kepplinger [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=1c16de8a-fed3-c7eb-b9c4-ceccae3d915d@ginzinger.com \
    --to=martin.kepplinger@ginzinger.com \
    --cc=bbrezillon@kernel.org \
    --cc=han.xu@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --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).