From: Boris Brezillon <boris.brezillon@collabora.com>
To: Przemyslaw Gaj <pgaj@cadence.com>
Cc: linux-i3c@lists.infradead.org, rafalc@cadence.com,
vitor.soares@synopsys.com
Subject: Re: [PATCH 1/4] i3c: Add support for mastership request to I3C subsystem
Date: Mon, 25 Feb 2019 09:51:05 +0100 [thread overview]
Message-ID: <20190225095105.542956b6@collabora.com> (raw)
In-Reply-To: <20190222210901.GA5138@global.cadence.com>
On Fri, 22 Feb 2019 21:09:03 +0000
Przemyslaw Gaj <pgaj@cadence.com> wrote:
> > > +
> > > +bool i3c_master_owns_bus_locked(struct i3c_master_controller *master)
> > > +{
> > > + return master->bus.cur_master == master->this;
> > > +}
> >
> > If you create the i3c_master_acquire_bus_ownership() helper, you
> > should need i3c_master_owns_bus_locked().
>
> Should or shouldn't? :-)
Shouldn't :P.
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2019-02-25 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:08 [PATCH 0/4] Add the I3C mastership request Przemyslaw Gaj
2019-02-18 13:08 ` [PATCH 1/4] i3c: Add support for mastership request to I3C subsystem Przemyslaw Gaj
2019-02-22 15:30 ` Boris Brezillon
2019-02-22 21:09 ` Przemyslaw Gaj
2019-02-25 8:51 ` Boris Brezillon [this message]
2019-02-18 13:08 ` [PATCH 2/4] i3c: master: cdns: add support for mastership request to Cadence I3C master driver Przemyslaw Gaj
2019-02-18 13:08 ` [PATCH 3/4] i3c: master: Add module author Przemyslaw Gaj
2019-02-18 13:08 ` [PATCH 4/4] MAINTAINERS: add myself as co-maintainer of I3C subsystem Przemyslaw Gaj
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=20190225095105.542956b6@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=linux-i3c@lists.infradead.org \
--cc=pgaj@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 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).