From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Andersson <andersson@kernel.org>,
Prashant Malani <pmalani@chromium.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: Daniel Scally <djrscally@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: [PATCH v2 3/5] device property: Constify parameter in fwnode_graph_is_endpoint()
Date: Wed, 28 Sep 2022 13:57:44 +0300 [thread overview]
Message-ID: <20220928105746.51208-4-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20220928105746.51208-1-andriy.shevchenko@linux.intel.com>
Constify parameter in fwnode_graph_is_endpoint() since it doesn't
alter anything related to it.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
include/linux/property.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/property.h b/include/linux/property.h
index 6f9d6604edc3..fe440211e529 100644
--- a/include/linux/property.h
+++ b/include/linux/property.h
@@ -406,7 +406,7 @@ struct fwnode_handle *fwnode_graph_get_remote_port(
struct fwnode_handle *fwnode_graph_get_remote_endpoint(
const struct fwnode_handle *fwnode);
-static inline bool fwnode_graph_is_endpoint(struct fwnode_handle *fwnode)
+static inline bool fwnode_graph_is_endpoint(const struct fwnode_handle *fwnode)
{
return fwnode_property_present(fwnode, "remote-endpoint");
}
--
2.35.1
next prev parent reply other threads:[~2022-09-28 10:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 10:57 [PATCH v2 0/5] device property: Consitify a few APIs and correct dev_fwnode() Andy Shevchenko
2022-09-28 10:57 ` [PATCH v2 1/5] device property: Keep dev_fwnode() and dev_fwnode_const() separate Andy Shevchenko
2022-09-28 11:05 ` Greg Kroah-Hartman
2022-09-30 14:30 ` Sakari Ailus
2022-09-30 14:43 ` Greg Kroah-Hartman
2022-10-03 11:02 ` Sakari Ailus
2022-10-03 15:07 ` Greg Kroah-Hartman
2022-10-03 16:17 ` Greg Kroah-Hartman
2022-10-03 20:08 ` Sakari Ailus
2022-10-04 7:55 ` Greg Kroah-Hartman
2022-10-04 8:14 ` Andy Shevchenko
2022-10-04 8:24 ` Greg Kroah-Hartman
2022-10-04 8:25 ` Andy Shevchenko
2022-10-04 9:21 ` Andy Shevchenko
2022-10-04 9:15 ` Sakari Ailus
2022-10-03 11:54 ` Rafael J. Wysocki
2022-10-03 12:00 ` Sakari Ailus
2022-10-03 15:05 ` Greg Kroah-Hartman
2022-09-28 10:57 ` [PATCH v2 2/5] device property: Constify fwnode connection match APIs Andy Shevchenko
2022-09-28 10:57 ` Andy Shevchenko [this message]
2022-09-28 10:57 ` [PATCH v2 4/5] device property: Constify device child node APIs Andy Shevchenko
2022-09-28 10:57 ` [PATCH v2 5/5] device property: Constify parameter in device_dma_supported() and device_get_dma_attr() Andy Shevchenko
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=20220928105746.51208-4-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andersson@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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.