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.3
Date: Wed, 1 Mar 2023 00:12:25 +0100	[thread overview]
Message-ID: <Y/6KWc1az70PQB+/@mail.local> (raw)

Hello Linus,

Here is the i3c subsytem pull request for 6.3. There are two small
improvements for this cycle.

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 510d2358c466bf6588034f0d3b2266eed2bc0a51:

  i3c: master: dw: stop hardcoding initial speed (2023-02-28 23:54:49 +0100)

----------------------------------------------------------------
I3C for 6.3

Subsystem:
 - transfer pid from boardinfo to device info

Drivers:
 - dw-i3c-master: stop hardcoding initial speed

----------------------------------------------------------------
Jack Chen (2):
      i3c: transfer pid from boardinfo to device info
      i3c: master: dw: stop hardcoding initial speed

 drivers/i3c/master.c               | 1 +
 drivers/i3c/master/dw-i3c-master.c | 5 +++--
 2 files changed, 4 insertions(+), 2 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:[~2023-02-28 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 23:12 Alexandre Belloni [this message]
2023-03-01  0:13 ` [GIT PULL] I3C changes for 6.3 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=Y/6KWc1az70PQB+/@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).