From: Jonathan Cameron <jic23@kernel.org>
To: NeilBrown <neilb@suse.de>, Sebastian Reichel <sre@debian.org>
Cc: 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: Sun, 24 Nov 2013 21:04:12 +0000 [thread overview]
Message-ID: <529269CC.3050007@kernel.org> (raw)
In-Reply-To: <20131119164839.7cd3f4f1@notabene.brown>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/19/13 05:48, NeilBrown wrote:
> 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.
Given that typically people will need to grep for the name of the actual
device they have to find the docs (not always obvious where in the documentation
their bindings will lie), it perhaps makes sense to put these simple devices
in trivial-devices.txt.
Anyhow, it is how it is currently done and we can always unwind it later to separate
files so, yes - please do move this and if missing add the invense entry as well
as Mark has requested.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSkmnMAAoJEFSFNJnE9BaI2QQP/R9wloBWmMKiuF+2MFD4qPSM
GCgKVVptzk/qgV1TYvj7OsuYigGkCcVdTptRg3uDgrg2gL/1beYz8HqbeIRALcCp
G2rPKhFGF9R6LalHUU0eMVGvvTqUe7J2gXCnxoINp0QM+fAyFfkMk5FZJJur4drI
GnwroRToRcrIRloIFNstDc5m5/jphshCB++sEDh/uTZT64ZcH5VKlcsHmuzMGOEm
VO/gebr5kHogGA54HUB4C8psrMJncKm3XFt57yq9tkhHkDk/VijDdROuhbOMY/K0
6eLLl7oIUkYtQ0AOowg2pDG3B5mvBexfi2W5JWf9yxiK/GBE54OQwyPNXWSeR4Jo
yLFs+anAtoNVYJuX5O0hs5NXzAJCAhcsXVggzKAmBY5IQkUZ5HzyBxwpH7aB1c1N
xZY89s1gx4Fke3GNPxqQ7tTDnFy5qZvnZ1/RM0F1j6D6zVMVSM5rRtjZrn3jdpue
gvzoYSV7f6la+BVj6S2tR2bEFkEssiaUkPn844e+EPZ+iSt8rLVD7WRA0M7bVp4t
R5ruRioF7D3LGzSfJwhna5/SNCytKuUBKc98PL0VZRx1707GAa2Ucl/YAIp/Gnkh
ERq9T5GbeT+9zMAfQpeE7Jaz+CwrS8ib0ul+IZzA9q+CqOdZZo3/xjdkQjSw9D9C
IL28pFxuFOKYabdZ9kQC
=EsOI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-11-24 21:04 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
2013-11-24 21:04 ` Jonathan Cameron [this message]
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=529269CC.3050007@kernel.org \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=mark.rutland@arm.com \
--cc=neilb@suse.de \
--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).