From: Boris Brezillon <bbrezillon@kernel.org>
To: Przemyslaw Gaj <pgaj@cadence.com>
Cc: linux-i3c@lists.infradead.org, psroka@cadence.com,
rafalc@cadence.com, vitor.soares@synopsys.com
Subject: Re: [PATCH 0/2] Add the I3C mastership request
Date: Thu, 13 Dec 2018 13:47:05 +0100 [thread overview]
Message-ID: <20181213134705.7d33dd3e@bbrezillon> (raw)
In-Reply-To: <cover.1544703840.git.pgaj@cadence.com>
Hi Przemek,
When you resend a patch or a series, you should prefix it with [PATCH
RESEND] and explain why you're resending it.
On Thu, 13 Dec 2018 12:27:59 +0000
Przemyslaw Gaj <pgaj@cadence.com> wrote:
> This patch series adds support for mastership request to I3C
> subsystem and Cadence I3C master driver. Mastership request
> allows slave to become the master of the I3C bus.
Thanks for working on that.
>
> Przemyslaw Gaj (2):
> i3c: Add support for mastership request to I3C subsystem
> i3c: master: cdns: add support for mastership request to Cadence I3C
> master driver.
>
> drivers/i3c/master.c | 260 ++++++++++++++++++++++++++--
> drivers/i3c/master/i3c-master-cdns.c | 316 ++++++++++++++++++++++++++++++-----
> include/linux/i3c/master.h | 43 ++++-
> 3 files changed, 560 insertions(+), 59 deletions(-)
>
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2018-12-13 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:27 [PATCH 0/2] Add the I3C mastership request Przemyslaw Gaj
2018-12-13 12:28 ` [PATCH 1/2] i3c: Add support for mastership request to I3C subsystem Przemyslaw Gaj
2018-12-13 13:50 ` Boris Brezillon
2018-12-14 7:14 ` Przemyslaw Gaj
2018-12-14 8:24 ` Boris Brezillon
2018-12-14 13:47 ` Przemyslaw Gaj
2018-12-19 14:16 ` Boris Brezillon
2018-12-13 12:28 ` [PATCH 2/2] i3c: master: cdns: add support for mastership request to Cadence I3C master driver Przemyslaw Gaj
2018-12-13 12:47 ` Boris Brezillon [this message]
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=20181213134705.7d33dd3e@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=pgaj@cadence.com \
--cc=psroka@cadence.com \
--cc=rafalc@cadence.com \
--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.