From: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c <linux-i3c@lists.infradead.org>,
Przemyslaw Gaj <pgaj@cadence.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vitor Soares <vitor.soares@synopsys.com>
Subject: [GIT PULL] i3c: Changes for 5.2
Date: Mon, 6 May 2019 08:58:35 +0200 [thread overview]
Message-ID: <20190506085835.61688fd2@collabora.com> (raw)
Hello Linus,
Here is the I3C PR for 5.2.
Regards,
Boris
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-5.2
for you to fetch changes up to 476c7e1d34f2a03b1aa5a924c50703053fe5f77c:
i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status() (2019-05-06 08:15:02 +0200)
----------------------------------------------------------------
* Fix a shift wrap bug in the core
* Remove dead code in the DW driver
----------------------------------------------------------------
Dan Carpenter (1):
i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status()
Vitor Soares (1):
i3c: master: dw: remove dead code from dw_i3c_master_*_xfers()
drivers/i3c/master.c | 5 +++--
drivers/i3c/master/dw-i3c-master.c | 10 ----------
2 files changed, 3 insertions(+), 12 deletions(-)
_______________________________________________
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: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vitor Soares <vitor.soares@synopsys.com>,
Przemyslaw Gaj <pgaj@cadence.com>
Subject: [GIT PULL] i3c: Changes for 5.2
Date: Mon, 6 May 2019 08:58:35 +0200 [thread overview]
Message-ID: <20190506085835.61688fd2@collabora.com> (raw)
Hello Linus,
Here is the I3C PR for 5.2.
Regards,
Boris
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-5.2
for you to fetch changes up to 476c7e1d34f2a03b1aa5a924c50703053fe5f77c:
i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status() (2019-05-06 08:15:02 +0200)
----------------------------------------------------------------
* Fix a shift wrap bug in the core
* Remove dead code in the DW driver
----------------------------------------------------------------
Dan Carpenter (1):
i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status()
Vitor Soares (1):
i3c: master: dw: remove dead code from dw_i3c_master_*_xfers()
drivers/i3c/master.c | 5 +++--
drivers/i3c/master/dw-i3c-master.c | 10 ----------
2 files changed, 3 insertions(+), 12 deletions(-)
next reply other threads:[~2019-05-06 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 6:58 Boris Brezillon [this message]
2019-05-06 6:58 ` [GIT PULL] i3c: Changes for 5.2 Boris Brezillon
2019-05-07 17:20 ` pr-tracker-bot
2019-05-07 17:20 ` 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=20190506085835.61688fd2@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgaj@cadence.com \
--cc=torvalds@linux-foundation.org \
--cc=vitor.soares@synopsys.com \
/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.