public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jesper Nilsson <jespern@axis.com>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Mikael Starvik <starvik@axis.com>,
	linux-cris-kernel <linux-cris-kernel@axis.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CRISv32: ETRAX_SPI_MMC_BOARD
Date: Wed, 29 Oct 2014 10:33:20 +0100	[thread overview]
Message-ID: <20141029093320.GQ30087@axis.com> (raw)
In-Reply-To: <1414570854.28499.34.camel@x220>

On Wed, Oct 29, 2014 at 09:20:54AM +0100, Paul Bolle wrote:
> Jesper,

Hi Paul!

> Your commit be64c1ce6e79 ("CRISv32: Drop obsolete file for SPI driver")
> landed in today's linux-next (ie, next-20141029). It removes the last
> user of the Kconfig symbol ETRAX_SPI_MMC_BOARD. Setting that symbol is
> now pointless.
> 
> Is the trivial patch to remove the entry for ETRAX_SPI_MMC_BOARD (and
> one select statement for it) queued somewhere? If not, should I submit
> it?

It was not, but it is now:

CRISv32: Remove last remnants of ETRAX_SPI_MMC_BOARD

There are no users of this symbol left.

Reported-by: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com>
---
 arch/cris/arch-v32/drivers/Kconfig |    7 -------
 1 file changed, 7 deletions(-)

diff --git a/arch/cris/arch-v32/drivers/Kconfig b/arch/cris/arch-v32/drivers/Kconfig
index 6880f94..7068c4b 100644
--- a/arch/cris/arch-v32/drivers/Kconfig
+++ b/arch/cris/arch-v32/drivers/Kconfig
@@ -361,13 +361,6 @@ config ETRAX_SPI_MMC
 	default MMC
 	select SPI
 	select MMC_SPI
-	select ETRAX_SPI_MMC_BOARD
-
-# For the parts that can't be a module (due to restrictions in
-# framework elsewhere).
-config ETRAX_SPI_MMC_BOARD
-       boolean
-       default n
 
 # While the board info is MMC_SPI only, the drivers are written to be
 # independent of MMC_SPI, so we'll keep SPI non-dependent on the
-- 
1.7.10.4


I'll try to think about unreferenced kconfigs in the future,
my suspicion is that all those SPI and MMC related configs are
also unused, just circular references keeping them unnoticed.

Thanks for the heads up.

> Paul Bolle

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  reply	other threads:[~2014-10-29  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  8:20 CRISv32: ETRAX_SPI_MMC_BOARD Paul Bolle
2014-10-29  9:33 ` Jesper Nilsson [this message]
2014-10-29  9:56   ` Paul Bolle

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=20141029093320.GQ30087@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=starvik@axis.com \
    --cc=valentinrothberg@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