Linux-i3c Archive on lore.kernel.org
 help / color / Atom feed
From: Vitor Soares <Vitor.Soares@synopsys.com>
To: Vitor Soares <Vitor.Soares@synopsys.com>,
	"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Cc: Joao Pinto <Joao.Pinto@synopsys.com>,
	"bbrezillon@kernel.org" <bbrezillon@kernel.org>
Subject: RE: [PATCH] i3c: master: use i3c_dev_get_master()
Date: Tue, 17 Sep 2019 09:42:07 +0000
Message-ID: <SN6PR12MB265578DF9D15725F93D7E568AE8F0@SN6PR12MB2655.namprd12.prod.outlook.com> (raw)
In-Reply-To: <a9d994b78d50a21e4eeb3a92004c56e68bb52e79.1567681102.git.vitor.soares@synopsys.com>

Hi Boris,

Friendly ping.

Best regards,
Vitor Soares

-----Original Message-----
From: Vitor Soares <vitor.soares@synopsys.com> 

Sent: Thursday, September 5, 2019 12:07 PM
To: 
linux-i3c@lists.infradead.org
Cc: bbrezillon@kernel.org; Joao Pinto 
<jpinto@synopsys.com>; Vitor Soares <vitor.soares@synopsys.com>
Subject: 
[PATCH] i3c: master: use i3c_dev_get_master()

Since we have i3c_dev_get_master() available, use it.

Signed-off-by: Vitor Soares <vitor.soares@synopsys.com>
---
 
drivers/i3c/master.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index 5f4bd52..d54039a 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -1779,7 +1779,7 @@ static void i3c_master_bus_cleanup(struct 
i3c_master_controller *master)
 static struct i3c_dev_desc *
 i3c_master_search_i3c_dev_duplicate(struct i3c_dev_desc *refdev)
 {
-	struct i3c_master_controller *master = refdev->common.master;
+	struct i3c_master_controller *master = i3c_dev_get_master(refdev);
 	struct i3c_dev_desc *i3cdev;
 
 	i3c_bus_for_each_i3cdev(&master->bus, i3cdev) {
-- 
2.7.4


_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 11:06 Vitor Soares
2019-09-17  9:42 ` Vitor Soares [this message]

Reply instructions:

You may reply publically 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=SN6PR12MB265578DF9D15725F93D7E568AE8F0@SN6PR12MB2655.namprd12.prod.outlook.com \
    --to=vitor.soares@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=bbrezillon@kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    /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

Linux-i3c Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-i3c/0 linux-i3c/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-i3c linux-i3c/ https://lore.kernel.org/linux-i3c \
		linux-i3c@lists.infradead.org linux-i3c@archiver.kernel.org
	public-inbox-index linux-i3c

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-i3c


AGPL code for this site: git clone https://public-inbox.org/ public-inbox