From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices
Date: Wed, 12 Feb 2014 16:15:43 +0100 [thread overview]
Message-ID: <20140212151543.GA10871@katana> (raw)
In-Reply-To: <20140210122119.115858a7ntu4lr40@67.228.131.205>
> There is now also a means to instantiate I2C devices through
> ACPI. This is documented in Documentation/acpi/enumeration.txt.
>
> Might be worthwhile to reference it from instantiating-devices.
> I guess that would be a separate patch though.
Yes, it would. Thanks for the pointer!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140212/c425f758/attachment.sig>
next prev parent reply other threads:[~2014-02-12 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 10:03 [PATCH 00/17] i2c: deprecate class based instantiation for embedded I2C drivers Wolfram Sang
2014-02-10 10:03 ` [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices Wolfram Sang
2014-02-10 18:21 ` linux at roeck-us.net
2014-02-12 15:15 ` Wolfram Sang [this message]
2014-02-15 14:48 ` Wolfram Sang
2014-02-10 10:03 ` [PATCH 02/17] i2c: add deprecation warning for class based instantiation Wolfram Sang
2014-02-10 10:04 ` [PATCH 10/17] i2c: i2c-nomadik: deprecate " Wolfram Sang
2014-02-12 16:24 ` Linus Walleij
2014-02-10 10:04 ` [PATCH 13/17] i2c: i2c-s3c2410: " Wolfram Sang
2014-02-10 10:04 ` [PATCH 14/17] i2c: i2c-sirf: " Wolfram Sang
2014-02-10 10:04 ` [PATCH 15/17] i2c: i2c-stu300: " Wolfram Sang
2014-02-12 16:22 ` Linus Walleij
2014-03-28 7:55 ` [PATCH 00/17] i2c: deprecate class based instantiation for embedded I2C drivers Wolfram Sang
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=20140212151543.GA10871@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).