linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL REQUEST] i2c for 3.14
Date: Sat, 15 Feb 2014 21:36:14 +0100	[thread overview]
Message-ID: <20140215203610.GA20244@katana> (raw)

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

Linus,

i2c has a bugfix and documentation improvements for you. Please pull.

Thanks,

   Wolfram


The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed:

  Linux 3.14-rc2 (2014-02-09 18:15:47 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current

for you to fetch changes up to fde1e418ab2c4269035f7f576e678b6ad3117d7d:

  Documentation: i2c: mention ACPI method for instantiating devices (2014-02-15 19:46:34 +0100)

----------------------------------------------------------------
Wolfram Sang (3):
      i2c: mv64xxx: refactor message start to ensure proper initialization
      Documentation: i2c: describe devicetree method for instantiating devices
      Documentation: i2c: mention ACPI method for instantiating devices

 Documentation/i2c/instantiating-devices | 41 +++++++++++++++++++++++++++++++--
 drivers/i2c/busses/i2c-mv64xxx.c        | 33 +++++++++++---------------
 2 files changed, 53 insertions(+), 21 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2014-02-15 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 20:36 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-27 17:43 [PULL REQUEST] i2c for 3.14 Wolfram Sang
2014-03-13 21:41 Wolfram Sang
2014-01-29 12:46 Wolfram Sang
2014-01-20 18:54 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=20140215203610.GA20244@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).