LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Daniel Scally <djrscally@gmail.com> To: linux-kernel@vger.kernel.org Cc: gregkh@linuxfoundation.org, rafael@kernel.org, andriy.shevchenko@linux.intel.com, laurent.pinchart@ideasonboard.com Subject: [PATCH v2 0/2] Check for endpoints in fwnode->secondary more sensibly Date: Thu, 5 Aug 2021 00:03:11 +0100 [thread overview] Message-ID: <20210804230313.78238-1-djrscally@gmail.com> (raw) Hello all A while ago I patched fwnode_graph_get_endpoint_by_id() to check for endpoints against fwnode->secondary if none was found against the primary. It's actually better to do this in fwnode_graph_get_next_endpoint() instead, since that function is called by fwnode_graph_get_endpoint_by_id() and also directly called in a bunch of other places (primarily sensor drivers checking that they have endpoints connected during probe). This small series just adds the equivalent functionality to fwnode_graph_get_next_endpoint() and reverts the earlier commit. Thanks Dan Daniel Scally (2): device property: Check fwnode->secondary in fwnode_graph_get_next_endpoint() Revert "media: device property: Call fwnode_graph_get_endpoint_by_id() for fwnode->secondary" drivers/base/property.c | 30 +++++++++++++++++++++--------- 1 file changed, 21 insertions(+), 9 deletions(-) -- 2.25.1
next reply other threads:[~2021-08-04 23:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 23:03 Daniel Scally [this message] 2021-08-04 23:03 ` [PATCH v2 1/2] device property: Check fwnode->secondary in fwnode_graph_get_next_endpoint() Daniel Scally 2021-08-04 23:03 ` [PATCH v2 2/2] Revert "media: device property: Call fwnode_graph_get_endpoint_by_id() for fwnode->secondary" Daniel Scally 2021-08-05 8:38 ` Greg KH 2021-08-05 8:59 ` Daniel Scally
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=20210804230313.78238-1-djrscally@gmail.com \ --to=djrscally@gmail.com \ --cc=andriy.shevchenko@linux.intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-kernel@vger.kernel.org \ --cc=rafael@kernel.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: linkBe 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).