diff options
| author | Brian Norris | 2013-03-13 17:51:31 +0100 |
|---|---|---|
| committer | David Woodhouse | 2013-03-14 13:48:54 +0100 |
| commit | 5bc7c33ca93a285dcfe7b7fd64970f6314440ad1 (patch) | |
| tree | 0ce80c4e6559c939c2eaf86c76950b177c4c157a /fs | |
| parent | mtd: bcm47xxpart: look for NVRAM at the end of device (diff) | |
| download | kernel-qcow2-linux-5bc7c33ca93a285dcfe7b7fd64970f6314440ad1.tar.gz kernel-qcow2-linux-5bc7c33ca93a285dcfe7b7fd64970f6314440ad1.tar.xz kernel-qcow2-linux-5bc7c33ca93a285dcfe7b7fd64970f6314440ad1.zip | |
mtd: nand: reintroduce NAND_NO_READRDY as NAND_NEED_READRDY
This partially reverts commit 1696e6bc2ae83734e64e206ac99766ea19e9a14e
("mtd: nand: kill NAND_NO_READRDY").
In that patch I overlooked a few things.
The original documentation for NAND_NO_READRDY included "True for all
large page devices, as they do not support autoincrement." I was
conflating "not support autoincrement" with the NAND_NO_AUTOINCR option,
which was in fact doing nothing. So, when I dropped NAND_NO_AUTOINCR, I
concluded that I then could harmlessly drop NAND_NO_READRDY. But of
course the fact the NAND_NO_AUTOINCR was doing nothing didn't mean
NAND_NO_READRDY was doing nothing...
So, NAND_NO_READRDY is re-introduced as NAND_NEED_READRDY and applied
only to those few remaining small-page NAND which needed it in the first
place.
Cc: stable@kernel.org [3.5+]
Reported-by: Alexander Shiyan <shc_work@mail.ru>
Tested-by: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions