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: Fixes for 5.1-rc6
Date: Sat, 20 Apr 2019 11:23:40 +0200 [thread overview]
Message-ID: <20190420112340.24be3932@collabora.com> (raw)
Hello Linus,
Here is the I3C fixes PR for 5.1-rc6.
Regards,
Boris
The following changes since commit 15ade5d2e7775667cf191cf2f94327a4889f8b9d:
Linux 5.1-rc4 (2019-04-07 14:09:59 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/fixes-for-5.1-rc6
for you to fetch changes up to 709a53e1948494cc4f6c4636c6f84a4d36a8117e:
MAINTAINERS: Fix the I3C entry (2019-04-10 12:47:55 +0200)
----------------------------------------------------------------
- Fix the random PID check
- Fix the disable controller logic in the designware driver
- Fix I3C entry in MAINTAINERS
----------------------------------------------------------------
Boris Brezillon (1):
MAINTAINERS: Fix the I3C entry
Vitor Soares (2):
i3c: Fix the verification of random PID
i3c: dw: Fix dw_i3c_master_disable controller by using correct mask
MAINTAINERS | 1 -
drivers/i3c/master.c | 5 ++---
drivers/i3c/master/dw-i3c-master.c | 2 +-
3 files changed, 3 insertions(+), 5 deletions(-)
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2019-04-20 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 9:23 Boris Brezillon [this message]
2019-04-20 19:25 ` [GIT PULL] i3c: Fixes for 5.1-rc6 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=20190420112340.24be3932@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 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).