linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: linux-pcmcia <linux-pcmcia@lists.infradead.org>,
	Linux-MIPS <linux-mips@linux-mips.org>,
	Florian Fainelli <florian@openwrt.org>,
	Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH] Alchemy: XXS1500 PCMCIA driver rewrite
Date: Sat, 3 Oct 2009 12:22:21 +0200	[thread overview]
Message-ID: <20091003102221.GB24206@pengutronix.de> (raw)
In-Reply-To: <f861ec6f0910020732p2ff76990q1e7a2bca16e52e64@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

> > Yeah, I saw that you want to remove it, still I don't know why :) Is it feature
> > incomplete and updating is impossible? Is the concept outdated? Could you
> > enlighten me on that?
> 
> I started out with the intention to fix its styling issues, add carddetect irq
> support, etc.  In the end it was easier to write a quick-and-dirty standalone
> full-features socket driver for the DB1200 and extend it to support the
> other DB/PB boards. While I was at it I modified my driver for the xxs1500,
> that's all.

Okay, that explains.

> 
> The only *technical* reason I have is a personal dislike for how the current
> one works: it forces every conceivable board to add dozens of cpp macros
> for mem/io ranges and gets registered by board-independent code.
> Hardly convincing, I know.

Well, you have the (to me) pretty convincing technical argument that your
drivers provide more features and less crashes which is a clear benefit for
users. If we remove the generic au1000-part, then it might even be in the same
amount in LoC. Okay, we lose a bit of maintainability if a bug is found in a
section which was shared among the former users of generic, as it has to be
updated for each of the three drivers, but well... Are there any plans to
convert pb1x00 as well?

Maybe I find time to look a bit more into it, but I can't test anything, of
course, so the more additional comments/test-reports the better.

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-10-03 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 18:50 [PATCH] Alchemy: XXS1500 PCMCIA driver rewrite Manuel Lauss
2009-09-29 19:46 ` Florian Fainelli
2009-10-02 10:59 ` Wolfram Sang
2009-10-02 11:15   ` Manuel Lauss
2009-10-02 12:54     ` Wolfram Sang
2009-10-02 14:32       ` Manuel Lauss
2009-10-03 10:22         ` Wolfram Sang [this message]
2009-10-03 11:49           ` Manuel Lauss
2009-10-03 14:03             ` Ralf Baechle
2009-10-03 14:36               ` Manuel Lauss

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=20091003102221.GB24206@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=manuel.lauss@gmail.com \
    --cc=manuel.lauss@googlemail.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;
as well as URLs for NNTP newsgroup(s).