mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: Get rid of SPI_BUTTERFLY duplication.
Date: Mon, 23 Jan 2006 06:23:57 -0800	[thread overview]
Message-ID: <200601230623.57691.david-b@pacbell.net> (raw)
In-Reply-To: <20060123134739.GA4172@linux-sh.org>

On Monday 23 January 2006 5:47 am, Paul Mundt wrote:
> CONFIG_SPI_BUTTERFLY is listed twice in drivers/spi/Kconfig, one will do
> fine..

Patch already sent to Linus, but thanks.  (Basically, a patch got
dropped, and this was one of the more visible symptoms.)

- dave


> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> 
> ---
> 
>  drivers/spi/Kconfig |   10 ----------
>  1 file changed, 10 deletions(-)
> 
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index b77dbd6..7a75fae 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -75,16 +75,6 @@ config SPI_BUTTERFLY
>  	  inexpensive battery powered microcontroller evaluation board.
>  	  This same cable can be used to flash new firmware.
>  
> -config SPI_BUTTERFLY
> -	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
> -	depends on SPI_MASTER && PARPORT && EXPERIMENTAL
> -	select SPI_BITBANG
> -	help
> -	  This uses a custom parallel port cable to connect to an AVR
> -	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
> -	  inexpensive battery powered microcontroller evaluation board.
> -	  This same cable can be used to flash new firmware.
> -
>  #
>  # Add new SPI master controllers in alphabetical order above this line
>  #
> 

      reply	other threads:[~2006-01-23 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 13:47 Paul Mundt
2006-01-23 14:23 ` David Brownell [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=200601230623.57691.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®