From: NeilBrown <neilb@suse.de>
To: Sebastian Reichel <sre@debian.org>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
Grant Likely <grant.likely@linaro.org>,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] itg3200: add dt support.
Date: Tue, 19 Nov 2013 16:48:39 +1100 [thread overview]
Message-ID: <20131119164839.7cd3f4f1@notabene.brown> (raw)
In-Reply-To: <20131119014938.GA20782@earth.universe>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Tue, 19 Nov 2013 02:49:38 +0100 Sebastian Reichel <sre@debian.org> wrote:
> Hi,
>
> On Tue, Nov 19, 2013 at 11:30:13AM +1100, NeilBrown wrote:
> > No new configuration, just a 'compatible' string and
> > documentation.
>
> itg3200 looks like a candidate for the list of trivial i2c
> devices [0] to me.
>
> [0] Documentation/devicetree/bindings/i2c/trivial-devices.txt
>
> -- Sebastian
Hmmm... a file that isn't referenced anywhere else in the kernel
documentation so is unlikely to be found except by people who know it is
there....
I can see that having lots of files for trivial devices is rather clumsy, but
there must be a better way.
I don't suppose we could just put the documentation in the device-driver file
in some format similar to kernel-doc and just extract it if it is wanted
separately? I think people read code a lot more than they read
documentation. I know I do.
But I can re-send with an update to trivial-devices.txt is that is what is
wanted.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-11-19 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 0:30 [PATCH v2] itg3200: add dt support NeilBrown
2013-11-19 1:49 ` Sebastian Reichel
2013-11-19 5:48 ` NeilBrown [this message]
2013-11-24 21:04 ` Jonathan Cameron
2013-11-19 9:59 ` Mark Rutland
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=20131119164839.7cd3f4f1@notabene.brown \
--to=neilb@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=mark.rutland@arm.com \
--cc=sre@debian.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).