From: Stefan Agner <stefan@agner.ch>
To: miquel.raynal@free-electrons.com, boris.brezillon@free-electrons.com
Cc: computersforpeace@gmail.com, dwmw2@infradead.org,
marek.vasut@gmail.com, cyrille.pitchen@wedev4u.fr,
richard@nod.at, bpringlemeir@gmail.com,
marcel.ziswiler@toradex.com, linux-mtd@lists.infradead.org,
stefan@agner.ch
Subject: [PATCH v6 3/3] mtd: rawnand: vf610_nfc: support ONFI SET/GET_FEATURES commands
Date: Sat, 3 Mar 2018 23:22:37 +0100 [thread overview]
Message-ID: <20180303222237.902-4-stefan@agner.ch> (raw)
In-Reply-To: <20180303222237.902-1-stefan@agner.ch>
With the move to ->exec_op() the driver should now support ONFI
SET/GET_FEATURES commands.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/mtd/nand/raw/vf610_nfc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/mtd/nand/raw/vf610_nfc.c b/drivers/mtd/nand/raw/vf610_nfc.c
index 4f2e8578fb1d..98d411d980c8 100644
--- a/drivers/mtd/nand/raw/vf610_nfc.c
+++ b/drivers/mtd/nand/raw/vf610_nfc.c
@@ -805,8 +805,6 @@ static int vf610_nfc_probe(struct platform_device *pdev)
chip->exec_op = vf610_nfc_exec_op;
chip->select_chip = vf610_nfc_select_chip;
- chip->onfi_set_features = nand_onfi_get_set_features_notsupp;
- chip->onfi_get_features = nand_onfi_get_set_features_notsupp;
chip->options |= NAND_NO_SUBPAGE_WRITE;
--
2.16.2
prev parent reply other threads:[~2018-03-03 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 22:22 [PATCH v6 0/3] mtd: rawnand: vf610_nfc: make use of ->exec_op() Stefan Agner
2018-03-03 22:22 ` [PATCH v6 1/3] " Stefan Agner
2018-03-05 16:28 ` Boris Brezillon
2018-03-03 22:22 ` [PATCH v6 2/3] mtd: rawnand: vf610_nfc: remove old hooks Stefan Agner
2018-03-03 22:22 ` Stefan Agner [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=20180303222237.902-4-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=bpringlemeir@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@free-electrons.com \
--cc=richard@nod.at \
/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