linux-kernel - Re: [PATCH 1/3] gpio / ACPI: add ACPI support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 05 Nov 2012 14:50:20 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	linux-kernel@...r.kernel.org, lenb@...nel.org,
	rafael.j.wysocki@...el.com, broonie@...nsource.wolfsonmicro.com,
	grant.likely@...retlab.ca, khali@...ux-fr.org, ben-linux@...ff.org,
	w.sang@...gutronix.de, linux-acpi@...r.kernel.org
Subject: Re: [PATCH 1/3] gpio / ACPI: add ACPI support

On Monday, November 05, 2012 02:28:45 PM Linus Walleij wrote:
> On Mon, Nov 5, 2012 at 2:19 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > On Monday, November 05, 2012 02:11:03 PM Linus Walleij wrote:
> >> Do you think they will change their mind and give me green light if
> >> I tell them I just need to do it right now? ;-)
> >
> > Well, it's just a matter of fairness to me, actually.
> >
> > If you allowed somebody to do something in the past, it's simply unfair
> > to forbid someone else to do a similar thing later, isn't it?
> 
> So if some subsystem has previously merged clk_get() for
> the silicon clock pertaining to a driver the maintainer should
> be fair to the pinctrl people and merge pinctrl_get() as well.

Well, let's just say if I were the maintainer of the subsystem in
question, I would propose a deal like this: I'm going to merge your
patches now, provided that you'll work on the centralized solution
going forward.  And it's quite easy to call them on the promise like
this in the future, when they ask you to merge something again.

> Well, they don't. But it wasn't any of your subsystems so
> I don't blame you.
> 
> I have been stand-in-maintaining the GPIO subsystem
> for the last two merge windows and I am worrying about the
> long term viability of the subsystem if we keep doing this
> without facing the real problem of the global GPIO
> numberspace.
> 
> But since Grant merged the gpiolib-of.c thing and is still the
> main maintainer I can atleast chicken out by referring to him
> this time ... hit me back if he doesn't respond and I will
> have to refactor the world or something.

No need to be grumpy. :-)

I forgot to mention that we want to hook up _existing_ drivers to those things,
and they already use the global GPIO numbers, don't they?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/