From: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-i3c <linux-i3c@lists.infradead.org>,
Vitor Soares <vitor.soares@synopsys.com>,
Przemyslaw Gaj <pgaj@cadence.com>
Subject: [GIT PULL] i3c: Changes for 5.1
Date: Fri, 1 Mar 2019 10:32:15 +0100 [thread overview]
Message-ID: <20190301103215.4ee6e758@collabora.com> (raw)
Hello Linus,
I know the merge window is not opened yet, but I'll be on vacation next
week, so I'm sending my I3C PR a bit earlier this time (already sent the
MTD one earlier this week, but for a different reason: I didn't check if
there was an -rc8 :)).
Regards,
Boris
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-5.1
for you to fetch changes up to 988bb4a1937bd083267444dda21b901dc6a959b3:
i3c: master: dw-i3c-master: mark expected switch fall-through (2019-02-28 09:47:53 +0100)
----------------------------------------------------------------
- Add a /* fall-through */ comment in the dw-i3c-master driver
- Update the I3C entries in MAINTAINERS to add an IRC chan
----------------------------------------------------------------
Boris Brezillon (1):
MAINTAINERS: Add an IRC channel for the I3C subsystem
Gustavo A. R. Silva (1):
i3c: master: dw-i3c-master: mark expected switch fall-through
MAINTAINERS | 1 +
drivers/i3c/master/dw-i3c-master.c | 1 +
2 files changed, 2 insertions(+)
next reply other threads:[~2019-03-01 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 9:32 Boris Brezillon [this message]
2019-03-05 3:40 ` [GIT PULL] i3c: Changes for 5.1 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=20190301103215.4ee6e758@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).