From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: Boris Brezillon <boris.brezillon@collabora.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v3 3/9] mtd: rawnand: onfi: Fix redundancy detection check
Date: Fri, 01 May 2020 02:55:19 +0000 [thread overview]
Message-ID: <20200501025520.133B821582@mail.kernel.org> (raw)
In-Reply-To: <20200428094302.14624-4-miquel.raynal@bootlin.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 39138c1f4a31 ("mtd: rawnand: use bit-wise majority to recover the ONFI param page").
The bot has tested the following trees: v5.6.7, v5.4.35, v4.19.118.
v5.6.7: Build OK!
v5.4.35: Build OK!
v4.19.118: Failed to apply! Possible dependencies:
0f808c1602bc ("mtd: rawnand: Pass a nand_chip object to chip->cmd_ctrl()")
1c325cc5077a ("mtd: rawnand: Move ONFI code to nand_onfi.c")
348d56a8c606 ("mtd: rawnand: Keep all internal stuff private")
3d4af7c19585 ("mtd: rawnand: Move legacy code to nand_legacy.c")
45240367939b ("mtd: rawnand: Deprecate ->{set,get}_features() hooks")
47bd59e538d4 ("mtd: rawnand: plat_nand: Pass a nand_chip object to all platform_nand_ctrl hooks")
716bbbabcc68 ("mtd: rawnand: Deprecate ->{read, write}_{byte, buf}() hooks")
7e534323c416 ("mtd: rawnand: Pass a nand_chip object to chip->read_xxx() hooks")
82fc5099744e ("mtd: rawnand: Create a legacy struct and move ->IO_ADDR_{R, W} there")
c0739d85723a ("mtd: rawnand: Pass a nand_chip object to chip->write_xxx() hooks")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-05-01 2:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 9:42 [PATCH v3 0/9] Misc timing changes Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 1/9] mtd: rawnand: timings: Add mode information to the timings structure Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 2/9] mtd: rawnand: timings: Fix default tR_max and tCCS_min timings Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 3/9] mtd: rawnand: onfi: Fix redundancy detection check Miquel Raynal
2020-04-28 9:42 ` Miquel Raynal
2020-05-01 2:55 ` Sasha Levin [this message]
2020-05-10 20:05 ` Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 4/9] mtd: rawnand: onfi: Use intermediate variables to improve readability Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 5/9] mtd: rawnand: onfi: Define the number of parameter pages Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:42 ` [PATCH v3 6/9] mtd: rawnand: onfi: Avoid doing a copy of the parameter page Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:43 ` [PATCH v3 7/9] mtd: rawnand: onfi: Drop a useless parameter page read Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:43 ` [PATCH v3 8/9] mtd: rawnand: jedec: Define the number of parameter pages Miquel Raynal
2020-05-10 20:05 ` Miquel Raynal
2020-04-28 9:43 ` [PATCH v3 9/9] mtd: rawnand: jedec: Use intermediate variables to improve readability Miquel Raynal
2020-05-10 20:04 ` Miquel Raynal
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=20200501025520.133B821582@mail.kernel.org \
--to=sashal@kernel.org \
--cc=boris.brezillon@collabora.com \
/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.