linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-mtd@lists.infradead.org, linux-cris-kernel@axis.com
Subject: Re: [PATCH] mtd: Remove unused symbol CONFIG_MTDRAM_ABS_POS
Date: Sat, 9 Jul 2016 17:38:35 -0700	[thread overview]
Message-ID: <20160710003835.GA29572@localhost> (raw)
In-Reply-To: <20160603000627.GN7555@decadent.org.uk>

On Fri, Jun 03, 2016 at 01:06:27AM +0100, Ben Hutchings wrote:
> This has been unused, except as the condition for a fatal error, since
> commit c13cbf3b5086 ("[MTD] mtdram: Quick cleanup of the driver:") in
> 2.6.13 (!).
> 
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
>  arch/cris/arch-v10/drivers/axisflashmap.c |  2 +-
>  drivers/mtd/devices/Kconfig               | 12 ------------
>  2 files changed, 1 insertion(+), 13 deletions(-)

You missed a usage in arch/cris/arch-v32/drivers/axisflashmap.c. Applied
with the following diff:

diff --git a/arch/cris/arch-v32/drivers/axisflashmap.c b/arch/cris/arch-v32/drivers/axisflashmap.c
index bd10d3ba0949..87656c41fec7 100644
--- a/arch/cris/arch-v32/drivers/axisflashmap.c
+++ b/arch/cris/arch-v32/drivers/axisflashmap.c
@@ -320,7 +320,7 @@ static int __init init_axis_flash(void)
 	 * but its size must be configured as 0 so as not to conflict
 	 * with our usage.
 	 */
-#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0) || (CONFIG_MTDRAM_ABS_POS != 0)
+#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0)
 	if (!romfs_in_flash && !nand_boot) {
 		printk(KERN_EMERG "axisflashmap: Cannot create an MTD RAM "
 		       "device; configure CONFIG_MTD_MTDRAM with size = 0!\n");

      parent reply	other threads:[~2016-07-10  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  0:06 [PATCH] mtd: Remove unused symbol CONFIG_MTDRAM_ABS_POS Ben Hutchings
2016-06-03  7:43 ` Jesper Nilsson
2016-07-10  0:38 ` Brian Norris [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=20160710003835.GA29572@localhost \
    --to=computersforpeace@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-cris-kernel@axis.com \
    --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;
as well as URLs for NNTP newsgroup(s).