public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Yannick Fertré" <yannick.fertre@st.com>
Cc: kbuild-all@01.org, Andrzej Hajda <a.hajda@samsung.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	Yannick Fertre <yannick.fertre@st.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Benjamin Gaignard <benjamin.gaignard@st.com>,
	Philippe Cornu <philippe.cornu@st.com>
Subject: [RFC PATCH] drm/bridge: sii902x: sii902x_cec_init() can be static
Date: Sat, 30 Mar 2019 16:12:15 +0800	[thread overview]
Message-ID: <20190330081215.GA24391@lkp-kbuild01> (raw)
In-Reply-To: <1553862958-6454-1-git-send-email-yannick.fertre@st.com>


Fixes: 1402bda01406 ("drm/bridge: sii902x: initialize CEC device")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 sii902x.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/bridge/sii902x.c b/drivers/gpu/drm/bridge/sii902x.c
index d33c097..42a0a7a 100644
--- a/drivers/gpu/drm/bridge/sii902x.c
+++ b/drivers/gpu/drm/bridge/sii902x.c
@@ -482,7 +482,7 @@ static int sii902x_i2c_bypass_deselect(struct i2c_mux_core *mux, u32 chan_id)
 	return 0;
 }
 
-int sii902x_cec_init(struct device *dev, struct sii902x *sii902x)
+static int sii902x_cec_init(struct device *dev, struct sii902x *sii902x)
 {
 	struct i2c_client *client;
 	int ret;

      parent reply	other threads:[~2019-03-30  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 12:35 [PATCH] drm/bridge: sii902x: initialize CEC device Yannick Fertré
2019-03-30  8:12 ` kbuild test robot
2019-03-30  8:12 ` kbuild test robot [this message]

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=20190330081215.GA24391@lkp-kbuild01 \
    --to=lkp@intel.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@st.com \
    --cc=benjamin.gaignard@st.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=philippe.cornu@st.com \
    --cc=yannick.fertre@st.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