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]
Message-ID: <CACRpkdZJPH__FzsUmKnQhTOtJ1EstJ8K5LzhTXGUO_VSzrjLew@mail.gmail.com>
Date:	Mon, 4 Jun 2012 19:08:43 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	linux-kernel@...r.kernel.org, patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] gpiolib: wm8994: Use irq_domain mappings for gpios

On Sun, Jun 3, 2012 at 2:40 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:

> This has no practical impact at present since we don't support device tree
> so any user must have set an irq_base but this will in future allow a
> transition to device tree with minimal invasiveness.
>
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

Acked-by: Linus Walleij <linus.walleij@...aro.org>

I read some drivers/base/regmap code and I think I understand this stuff
now, but seriously, it's quite hard to see the forest with all these trees,
and regmap is actually one of the finest new things in recent kernels,
so can could we create
Documentation/driver-model/regmap.txt?

I think this document is needed... I would write it myself if I felt I
understood the regmap overall concepts well enough, but I'm
certain to get something wrong.

Yours,
Linus Walleij
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ