From: Ben Dooks <ben-linux@fluff.org>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] [NAND] S3C2410: cleanup compile
Date: Mon, 19 Jun 2006 09:29:50 +0100 [thread overview]
Message-ID: <20060619082950.GA14365@home.fluff.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 138 bytes --]
Remove two unused variables and update the comments
for the new NAND command code entries
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
[-- Attachment #2: 2617-mtd-nand-cleanup.patch --]
[-- Type: text/plain, Size: 1202 bytes --]
diff -urNp -X linux-2.6-bjd2/Documentation/dontdiff linux-2.6-bjd2/drivers/mtd/nand/s3c2410.c linux-2.6-bjd3/drivers/mtd/nand/s3c2410.c
--- linux-2.6-bjd2/drivers/mtd/nand/s3c2410.c 2006-06-19 09:24:03.000000000 +0100
+++ linux-2.6-bjd3/drivers/mtd/nand/s3c2410.c 2006-06-19 09:27:14.000000000 +0100
@@ -268,20 +268,16 @@ static void s3c2410_nand_select_chip(str
clk_disable(info->clk);
}
-/* command and control functions
- *
- * Note, these all use tglx's method of changing the IO_ADDR_W field
- * to make the code simpler, and use the nand layer's code to issue the
- * command and address sequences via the proper IO ports.
+/* s3c2410_nand_hwcontrol
*
+ * Issue command and address cycles to the chip
*/
static void s3c2410_nand_hwcontrol(struct mtd_info *mtd, int cmd,
unsigned int ctrl)
{
struct s3c2410_nand_info *info = s3c2410_nand_mtd_toinfo(mtd);
- struct nand_chip *chip = mtd->priv;
-
+
if (cmd == NAND_CMD_NONE)
return;
@@ -297,7 +293,6 @@ static void s3c2440_nand_hwcontrol(struc
unsigned int ctrl)
{
struct s3c2410_nand_info *info = s3c2410_nand_mtd_toinfo(mtd);
- struct nand_chip *chip = mtd->priv;
if (cmd == NAND_CMD_NONE)
return;
reply other threads:[~2006-06-19 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060619082950.GA14365@home.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-mtd@lists.infradead.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