Linux-i3c 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 6.2
Date: Wed, 14 Dec 2022 00:13:32 +0100	[thread overview]
Message-ID: <Y5kHHAOgXCz3zQzi@mail.local> (raw)

Hello Linus,

Here is the i3c subsytem pull request for 6.2. There is a non urgent fix
and SETDASA is now exported to drivers.

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 08dcf0732cb4d97b85493d9f60470e48eebf87fe:

  MAINTAINERS: mark I3C DRIVER FOR SYNOPSYS DESIGNWARE orphan (2022-12-11 22:04:58 +0100)

----------------------------------------------------------------
I3C for 6.2

Subsystem:
 - API changes

----------------------------------------------------------------
Alexandre Belloni (1):
      MAINTAINERS: mark I3C DRIVER FOR SYNOPSYS DESIGNWARE orphan

Jack Chen (1):
      i3c: export SETDASA method

Naveen Krishna Chatradhi (1):
      i3c: Correct the macro module_i3c_i2c_driver

 MAINTAINERS                |  3 +--
 drivers/i3c/device.c       | 20 ++++++++++++++++++++
 drivers/i3c/internals.h    |  1 +
 drivers/i3c/master.c       | 19 +++++++++++++++++++
 include/linux/i3c/device.h |  5 ++++-
 5 files changed, 45 insertions(+), 3 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-12-13 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 23:13 Alexandre Belloni [this message]
2022-12-14 18:04 ` [GIT PULL] I3C changes for 6.2 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=Y5kHHAOgXCz3zQzi@mail.local \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).