linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [GIT PULL] i2c: 'i2c-bus' node support for v4.8-rc1
Date: Fri,  1 Jul 2016 17:00:55 +0200	[thread overview]
Message-ID: <20160701150056.26537-2-thierry.reding@gmail.com> (raw)

Hi Wolfram,

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

  Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.8-i2c

for you to fetch changes up to 7e4c224abfe8e2a00f56a2ef0198e6de3ca1852c:

  i2c: core: Add support for 'i2c-bus' subnode (2016-06-30 11:02:17 +0200)

Thanks,
Thierry

----------------------------------------------------------------
i2c: 'i2c-bus' node support for v4.8-rc1

This includes the device tree binding and I2C core changes to support
the i2c-bus subnode that I2C masters can use to describe their slaves
in a separate namespace and therefore avoid clashing with potentially
other subnodes.

----------------------------------------------------------------
Jon Hunter (2):
      dt-bindings: i2c: Add support for 'i2c-bus' subnode
      i2c: core: Add support for 'i2c-bus' subnode

 Documentation/devicetree/bindings/i2c/i2c.txt |  8 ++++++++
 drivers/i2c/i2c-core.c                        | 10 ++++++++--
 2 files changed, 16 insertions(+), 2 deletions(-)

             reply	other threads:[~2016-07-01 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 15:00 Thierry Reding [this message]
2016-07-01 15:44 ` [GIT PULL] i2c: 'i2c-bus' node support for v4.8-rc1 Wolfram Sang
2016-10-10 12:46   ` Jon Hunter
2016-10-12  7:00     ` 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=20160701150056.26537-2-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).