From: Brian Norris <computersforpeace@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "Scott Branden" <sbranden@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>, "Rafał Miłecki" <zajec5@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Hauke Mehrtens" <hauke@hauke-m.de>,
linux-mtd@lists.infradead.org
Subject: [PATCH 3/3] mtd: brcmnand: remove unnecessary fields from brcmnand_soc
Date: Wed, 20 May 2015 17:05:06 -0700 [thread overview]
Message-ID: <1432166706-4320-3-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1432166706-4320-1-git-send-email-computersforpeace@gmail.com>
These really aren't needed, especially now that we embed the soc struct
in our private struct, so we can stash things there if needed.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
drivers/mtd/nand/brcmnand/brcmnand.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/mtd/nand/brcmnand/brcmnand.h b/drivers/mtd/nand/brcmnand/brcmnand.h
index a20c73630b7b..09a9043637b5 100644
--- a/drivers/mtd/nand/brcmnand/brcmnand.h
+++ b/drivers/mtd/nand/brcmnand/brcmnand.h
@@ -21,8 +21,6 @@ struct platform_device;
struct dev_pm_ops;
struct brcmnand_soc {
- struct platform_device *pdev;
- void *priv;
bool (*ctlrdy_ack)(struct brcmnand_soc *soc);
void (*ctlrdy_set_enabled)(struct brcmnand_soc *soc, bool en);
void (*prepare_data_bus)(struct brcmnand_soc *soc, bool prepare);
--
1.9.1
next prev parent reply other threads:[~2015-05-21 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 0:05 [PATCH 1/3] mtd: brcmnand: refactor bcm63138 SoC layering Brian Norris
2015-05-21 0:05 ` [PATCH 2/3] mtd: brcmnand: refactor iProc " Brian Norris
2015-05-21 0:05 ` Brian Norris [this message]
2015-09-30 20:08 ` [PATCH 1/3] mtd: brcmnand: refactor bcm63138 " Brian Norris
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=1432166706-4320-3-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=zajec5@gmail.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 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).