linux-i3c.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] I3C changes for 5.18
Date: Wed, 30 Mar 2022 00:27:36 +0200	[thread overview]
Message-ID: <YkOH2Jd9soaAFoog@piout.net> (raw)

Hello Linux,

Here is the pull request for the i3c subsystem, adding support to
dynamically add i2c devices on a bus.

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-5.18

for you to fetch changes up to 6cbf8b38dfe3aabe330f2c356949bc4d6a1f034f:

  i3c: fix uninitialized variable use in i2c setup (2022-03-08 22:33:52 +0100)

----------------------------------------------------------------
I3C for 5.18

Subsystem:
 - support dynamic addition of i2c devices

----------------------------------------------------------------
Jamie Iles (3):
      i3c: remove i2c board info from i2c_dev_desc
      i3c: support dynamically added i2c devices
      i3c: fix uninitialized variable use in i2c setup

 drivers/i3c/master.c       | 151 ++++++++++++++++++++++++++++++++++++++++++---
 include/linux/i3c/master.h |   1 -
 2 files changed, 142 insertions(+), 10 deletions(-)

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

             reply	other threads:[~2022-03-29 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 22:27 Alexandre Belloni [this message]
2022-03-30 18:20 ` [GIT PULL] I3C changes for 5.18 pr-tracker-bot

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=YkOH2Jd9soaAFoog@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).