public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: gpio-ucb1400
Date: Mon, 01 Apr 2013 13:06:43 +0200	[thread overview]
Message-ID: <1364814403.4943.7.camel@amber.site> (raw)
In-Reply-To: <201303311919.06030.marek.vasut@gmail.com>

Le dimanche 31 mars 2013 à 19:19 +0200, Marek Vasut a écrit :
> Dear Guenter Roeck,
> > Jean is absolutely right - it should get fixed, or the driver should be
> > dropped if no one is using it anyway.
> 
> I think ARM/palmtc was using this.

My point was, the upstream gpio-ucb1400 driver in its current form is
unusable (on top of being ugly.) I have no doubt that someone used that
driver successfully in some external kernel tree, but the code that was
merged upstream is incomplete and no good.

-- 
Jean Delvare
Suse L3


  reply	other threads:[~2013-04-01 11:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 19:46 gpio-ucb1400 Jean Delvare
2013-03-30 15:10 ` gpio-ucb1400 Guenter Roeck
2013-03-30 19:20   ` gpio-ucb1400 Marek Vasut
2013-03-30 23:25     ` gpio-ucb1400 Guenter Roeck
2013-03-31 17:19       ` gpio-ucb1400 Marek Vasut
2013-04-01 11:06         ` Jean Delvare [this message]
2013-04-01 15:32           ` gpio-ucb1400 Mark Brown
2013-04-02  7:22             ` gpio-ucb1400 Jean Delvare
2013-04-02  8:45               ` gpio-ucb1400 Mark Brown
2013-04-10 18:18               ` gpio-ucb1400 Linus Walleij
2013-04-14 18:35                 ` [PATCH v2] UCB1400: Pass ucb1400-gpio data through ac97 bus Marek Vasut
2013-04-14 18:40                   ` Marek Vasut
2013-04-15 11:15                   ` Mark Brown
2013-04-17 15:24                   ` Linus Walleij
2013-04-18 22:40                   ` Samuel Ortiz

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=1364814403.4943.7.camel@amber.site \
    --to=jdelvare@suse.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marek.vasut@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