All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, david-b@pacbell.net,
	Andrea Paterniani <a.paterniani@swapp-eng.it>
Subject: Re: [PATCH 1/2] remove i.MX SPI driver
Date: Wed, 24 Jun 2009 11:24:43 +0200	[thread overview]
Message-ID: <20090624092443.GW31396@pengutronix.de> (raw)
In-Reply-To: <20090623155840.c750b70b.akpm@linux-foundation.org>

On Tue, Jun 23, 2009 at 03:58:40PM -0700, Andrew Morton wrote:
> On Thu, 18 Jun 2009 08:54:31 +0200
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> > This driver is in a non working state at the moment and will
> > be replaced by a bitbang driver which can also handle the
> > newer i.MX variants
> 
> hum.  How did it get into a non-working state?
> 
> From the logs, it looks like it was working OK for Andrea Paterniani
> when he patched it in April last year.

The driver was written for arch-imx which is superseeded by arch-mxc
now. It depends on the i.MX DMA API which changed while moving from
arch-imx to arch-mxc.
A reason to keep the old driver is that it has DMA support, but Andrea
agrees that it's better to add DMA support to the new driver than to fix
it in the old driver.

> 
> Ordinarily I'd be asking whether this replacement of one driver with
> another is a 100% seamless change.  But I guess that the audience for
> SPI drivers are sufficiently technical to be able to handle the odd
> Kconfig changes, module parameter changes, module name changes, etc.
> 
> But I do think that if there are any such user-visible changes, they
> should be described in the changelog.  And I think there are such
> changes - the module name at least?
> 
> 
> Is it possible and desirable to retain both drivers for a while?  Would
> that ease the transition?  It also gives people a fallback driver to
> use, if your new driver doesn't work for them.  Just like eepro100.c,
> which lived for five years ;)

I rather try to avoid that. Note that this is a platform driver which
had zero inkernel users till now.

> 
> But it's really hard to make any decisions about this because the
> changelog failed to provide any details about the "non working state".
>

I'll add notes about this to the patch which removes the driver.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2009-06-24  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  6:54 Sascha Hauer
2009-06-18  6:54 ` [PATCH 1/2] remove i.MX SPI driver Sascha Hauer
2009-06-18  6:54   ` [PATCH 2/2] SPI: Add SPI driver for most known i.MX SoCs Sascha Hauer
2009-06-23 23:11     ` Andrew Morton
2009-06-24  9:09       ` Sascha Hauer
2009-06-23 22:58   ` [PATCH 1/2] remove i.MX SPI driver Andrew Morton
2009-06-24  9:24     ` Sascha Hauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-17 10:40 Sascha Hauer
     [not found] ` <1245235220-23816-1-git-send-email-s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-06-17 10:40   ` [PATCH 1/2] remove " Sascha Hauer

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=20090624092443.GW31396@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.paterniani@swapp-eng.it \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.