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.5
Date: Mon, 3 Jul 2023 00:04:54 +0200 [thread overview]
Message-ID: <202307022204546baff5fd@mail.local> (raw)
Hello Linus,
Here is the i3c subsytem pull request for 6.5. These are non-urgent
fixes for the svc driver.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-6.5
for you to fetch changes up to 49b472ebc61de3d4aa7cc57539246bb39f6c5128:
i3c: master: svc: add NACK check after start byte sent (2023-06-05 00:50:51 +0200)
----------------------------------------------------------------
I3C for 6.5
Drivers:
- svc: fix suspend/resume on some platforms, fix locking issues
----------------------------------------------------------------
Clark Wang (3):
i3c: master: svc: fix i3c suspend/resume issue
i3c: master: svc: fix cpu schedule in spin lock
i3c: master: svc: add NACK check after start byte sent
drivers/i3c/master/svc-i3c-master.c | 51 ++++++++++++++++++++++++++++++-------
1 file changed, 42 insertions(+), 9 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
WARNING: multiple messages have this Message-ID (diff)
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.5
Date: Mon, 3 Jul 2023 00:04:54 +0200 [thread overview]
Message-ID: <202307022204546baff5fd@mail.local> (raw)
Hello Linus,
Here is the i3c subsytem pull request for 6.5. These are non-urgent
fixes for the svc driver.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-6.5
for you to fetch changes up to 49b472ebc61de3d4aa7cc57539246bb39f6c5128:
i3c: master: svc: add NACK check after start byte sent (2023-06-05 00:50:51 +0200)
----------------------------------------------------------------
I3C for 6.5
Drivers:
- svc: fix suspend/resume on some platforms, fix locking issues
----------------------------------------------------------------
Clark Wang (3):
i3c: master: svc: fix i3c suspend/resume issue
i3c: master: svc: fix cpu schedule in spin lock
i3c: master: svc: add NACK check after start byte sent
drivers/i3c/master/svc-i3c-master.c | 51 ++++++++++++++++++++++++++++++-------
1 file changed, 42 insertions(+), 9 deletions(-)
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2023-07-02 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 22:04 Alexandre Belloni [this message]
2023-07-02 22:04 ` [GIT PULL] I3C changes for 6.5 Alexandre Belloni
2023-07-03 17:49 ` pr-tracker-bot
2023-07-03 17:49 ` 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=202307022204546baff5fd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.