From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] gpiolib: wm8994: Use irq_domain mappings for gpios
Date: Mon, 4 Jun 2012 18:11:30 +0100 [thread overview]
Message-ID: <20120604171130.GB23408@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdZJPH__FzsUmKnQhTOtJ1EstJ8K5LzhTXGUO_VSzrjLew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Mon, Jun 04, 2012 at 07:08:43PM +0200, Linus Walleij wrote:
> 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?
Of course, someone can!
> 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.
Well, there's one sure fire way to make sure you've got a good
understanding :)
More seriously I'm not sure I could readily tell what's non-obvious and
worth writing a document about. Personally I always just read the
commit logs for Linux stuff, they're some of the best documentation I've
ever seen for software.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-04 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 12:40 [PATCH] gpiolib: wm8994: Use irq_domain mappings for gpios Mark Brown
2012-06-04 17:08 ` Linus Walleij
2012-06-04 17:11 ` Mark Brown [this message]
2012-06-04 17:30 ` Jonathan Corbet
2012-06-04 18:05 ` Mark Brown
2012-07-05 12:38 ` 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=20120604171130.GB23408@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.