From: Robert ABEL <rabel@cit-ec.uni-bielefeld.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] GPIOD, OF: parse flags into gpiod
Date: Tue, 13 May 2014 13:33:09 +0200 [thread overview]
Message-ID: <537202F5.6070609@cit-ec.uni-bielefeld.de> (raw)
In-Reply-To: <CACRpkdZu0BAfR5b=-AbURxQ1VtGJbBmBwrTmLkO3Te--EHYWyQ@mail.gmail.com>
Hi Linus,
On 13 May 2014 10:42, Linus Walleij wrote:
> Since I've merged Alexandre's other patch making the function private
> I'm dropping this assuming you have sorted things out...
No, I just stopped responding, because I grew tired of his stupid argument.
You want broken functions, you get broken functions.
Alexandre's claim that
On 05 May 2014 17:14, Alexandre Courbot wrote:
> Good news, once of_get_gpiod_flags() becomes private all public gpiod_
> functions should return a correct gpio_desc.
is wrong, of course. And ridiculous, I might add.
None of the gpiod_* functions return valid gpio_desc with the singular
exception of gpiod_get, which happens to be aware of the shortcomings of
all other public functions and corrects their mistakes after the fact.
Regards,
Robert
next prev parent reply other threads:[~2014-05-13 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 12:38 [PATCH] GPIOD, OF: parse flags into gpiod Robert ABEL
2014-05-01 6:24 ` Alexandre Courbot
2014-05-05 10:07 ` Robert Abel
2014-05-05 10:27 ` Robert Abel
2014-05-05 13:10 ` Alexandre Courbot
2014-05-05 14:08 ` Robert ABEL
2014-05-05 15:14 ` Alexandre Courbot
2014-05-05 16:46 ` Alexandre Courbot
2014-05-13 12:19 ` Robert ABEL
2014-05-13 13:38 ` Javier Martinez Canillas
2014-05-14 0:44 ` Robert Abel
2014-05-14 4:09 ` Alexandre Courbot
2014-05-13 14:24 ` Alexandre Courbot
2014-05-16 15:49 ` Linus Walleij
2014-05-13 8:42 ` Linus Walleij
2014-05-13 11:33 ` Robert ABEL [this message]
2014-05-13 13:20 ` 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=537202F5.6070609@cit-ec.uni-bielefeld.de \
--to=rabel@cit-ec.uni-bielefeld.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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).