linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [RFC PATCH] gpiolib: Provide and export gpiod_export_name
Date: Tue, 12 Aug 2014 17:29:05 -0700	[thread overview]
Message-ID: <20140813002905.GA31412@roeck-us.net> (raw)
In-Reply-To: <CAAVeFuKE8z6JunJT-pE5wyjEBR5KvEUZoh5pASzhg1n2qsWcag@mail.gmail.com>

On Mon, Aug 11, 2014 at 03:05:54PM -0700, Alexandre Courbot wrote:
> On Mon, Aug 11, 2014 at 9:13 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> > On 08/11/2014 08:20 AM, Alexandre Courbot wrote:
> > [ ... ]
> >
> >>
> >> Note that this doesn't change anything to the core of the argument ;
> >> we have not heard what Linus thinks about named GPIOs in
> >> /sys/class/gpio yet, maybe he will have a different opinion...
> >>
> >
> > Well, please let me know if/when you are planning to take away
> > that existing ABI so I can plan accordingly. FWIW, out-of-kernel
> > users I am currently aware of are Juniper Networks and Zodiac
> > Aerospace. The latter asked me to help them upstreaming their code.
> >
> > If you plan to remove the ABI, you might want to inform its current
> > in-kernel users. You can look those up yourself.
> 
> We are not taking existing user-space ABIs away. But we are also not
> encouraging people to use bad ABIs by introducing new ways to use
> them, hence my restraint towards this patch.
> 

You bring it to the point. You believe that the gpio ABI, or maybe just
named gpio pins, is a bad idea. Nothing I am going to say will influence
that opinion; all we do is to keep turning in circles.

So let's stop wasting our time, agree to disagree, and move on.

Thanks,
Guenter

  reply	other threads:[~2014-08-13  0:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 18:12 [RFC PATCH] gpiolib: Provide and export gpiod_export_name Guenter Roeck
2014-07-24  5:44 ` Alexandre Courbot
2014-07-24  6:29   ` Jiří Prchal
2014-07-24  6:36     ` Guenter Roeck
2014-07-25  7:46       ` Jiří Prchal
2014-07-25 14:09         ` Guenter Roeck
2014-07-24  6:33   ` Guenter Roeck
2014-08-07  6:25     ` Alexandre Courbot
2014-08-07  7:34       ` Guenter Roeck
2014-08-11 15:01         ` Alexandre Courbot
2014-08-11 15:15           ` Guenter Roeck
2014-08-11 15:20             ` Alexandre Courbot
2014-08-11 16:13               ` Guenter Roeck
2014-08-11 22:05                 ` Alexandre Courbot
2014-08-13  0:29                   ` Guenter Roeck [this message]
2014-08-29  5:44               ` Linus Walleij
2014-08-29  5:54                 ` Guenter Roeck
2014-08-29 17:00                   ` Alexandre Courbot
2014-08-29 17:37                     ` Guenter Roeck
2014-08-31  0:57                       ` Alexandre Courbot
2014-09-05  8:46                         ` Linus Walleij

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=20140813002905.GA31412@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).