linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Johan Hovold <johan@kernel.org>,
	"Grygorii.Strashko@linaro.org" <grygorii.strashko@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpiolib: debugfs: display gpios requested as irq only
Date: Thu, 21 May 2015 16:34:01 +0200	[thread overview]
Message-ID: <20150521143401.GB30660@localhost> (raw)
In-Reply-To: <CACRpkdbupBQBsymB4wcC9XxbFJMhzxoZVXhyKxZT+xxuSxwifA@mail.gmail.com>

On Wed, May 20, 2015 at 09:21:16AM +0200, Linus Walleij wrote:
> On Tue, May 19, 2015 at 5:39 PM, Johan Hovold <johan@kernel.org> wrote:
> > On Tue, May 19, 2015 at 04:12:35PM +0200, Linus Walleij wrote:
> 
> >> What? If I wanted a stable interface I would use sysfs and document
> >> the ABI in Documentation/ABI/*.
> >>
> >> debugfs is not ABI.
> >
> > As I mentioned in my response to Grygorii, not everyone -- and most
> > notably apparently not even Linus Torvalds -- agrees on this:
> 
> Yeah I was sloppy I guess.
> 
> What I mean, precisely is that sysfs is ABI, whether documented or
> not.
> 
> Even debugfs is actually blurry, as per
> Documentation/filesystems/debugfs.txt:
> 
> "The debugfs filesystem is also intended to not serve as a stable
> ABI to user space; in theory, there are no stability constraints placed on
> files exported there.  The real world is not always so simple, though [1];
> even debugfs interfaces are best designed with the idea that they will need
> to be maintained forever."
> 
> But I haven't been bitten by it yet so that's why I allow some poetic
> license.

Yes, and the [1] reference in that quote is the LWN article I referred
to.

I also see you already "broke" that ABI in a similar way in 2013 with
d468bf9ecaab ("gpio: add API to be strict about GPIO IRQ usage") by
adding the IRQ field.

Your call. :)

Johan

  reply	other threads:[~2015-05-21 14:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 13:25 [PATCH] gpiolib: debugfs: display gpios requested as irq only grygorii.strashko
2015-05-18 11:02 ` Johan Hovold
2015-05-18 13:06   ` Grygorii.Strashko@linaro.org
2015-05-18 15:08     ` Johan Hovold
2015-05-18 15:17       ` Grygorii.Strashko@linaro.org
2015-05-18 15:58         ` Johan Hovold
2015-05-19 14:12         ` Linus Walleij
2015-05-19 14:37           ` Grygorii.Strashko@linaro.org
2015-05-19 14:50             ` Linus Walleij
2015-05-19 15:39           ` Johan Hovold
2015-05-20  7:21             ` Linus Walleij
2015-05-21 14:34               ` Johan Hovold [this message]
2015-05-19 14:28   ` Linus Walleij
2015-05-21 14:25     ` Johan Hovold
2015-05-21 20:33       ` Grygorii.Strashko@linaro.org
2015-05-24 17:12         ` Johan Hovold
2015-05-25 18:54           ` Grygorii.Strashko@linaro.org
2015-05-25 20:39             ` Johan Hovold
2015-06-01 13:09             ` Linus Walleij
2015-06-02 12:33               ` Grygorii.Strashko@linaro.org

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=20150521143401.GB30660@localhost \
    --to=johan@kernel.org \
    --cc=gnurou@gmail.com \
    --cc=grygorii.strashko@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).