From: kbuild test robot <lkp@intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
heikki.krogerus@intel.com, enric.balletbo@collabora.com,
bleung@chromium.org, Prashant Malani <pmalani@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: [RFC PATCH] platform/chrome: cros_typec_parse_port_props() can be static
Date: Fri, 7 Feb 2020 14:52:00 +0800 [thread overview]
Message-ID: <20200207065200.eevscpn4h7d7ocvr@f53c9c00458a> (raw)
In-Reply-To: <20200205205954.84503-2-pmalani@chromium.org>
Fixes: 2adbeaafa10e ("platform/chrome: Add Type C connector class driver")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
cros_ec_typec.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/platform/chrome/cros_ec_typec.c b/drivers/platform/chrome/cros_ec_typec.c
index fe5659171c2a85..9b83aa4d5456d4 100644
--- a/drivers/platform/chrome/cros_ec_typec.c
+++ b/drivers/platform/chrome/cros_ec_typec.c
@@ -25,9 +25,9 @@ struct cros_typec_data {
struct typec_port *ports[EC_USB_PD_MAX_PORTS];
};
-int cros_typec_parse_port_props(struct typec_capability *cap,
- struct fwnode_handle *fwnode,
- struct device *dev)
+static int cros_typec_parse_port_props(struct typec_capability *cap,
+ struct fwnode_handle *fwnode,
+ struct device *dev)
{
const char *buf;
int ret;
next prev parent reply other threads:[~2020-02-07 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:59 [PATCH 0/3] platform/chrome: Add Type C connector class driver Prashant Malani
2020-02-05 20:59 ` [PATCH 1/3] " Prashant Malani
2020-02-06 16:19 ` Enric Balletbo i Serra
2020-02-06 23:30 ` Prashant Malani
2020-02-07 17:00 ` Enric Balletbo i Serra
2020-02-07 20:28 ` Prashant Malani
2020-02-07 6:51 ` kbuild test robot
2020-02-07 6:52 ` kbuild test robot [this message]
2020-02-05 20:59 ` [PATCH 2/3] platform/chrome: typec: Get PD_CONTROL cmd version Prashant Malani
2020-02-05 20:59 ` [PATCH 3/3] platform/chrome: typec: Update port info from EC Prashant Malani
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=20200207065200.eevscpn4h7d7ocvr@f53c9c00458a \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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
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).