From: kbuild test robot <lkp@intel.com>
To: "Carlos E. C. Barbosa" <climacobarbosacee@gmail.com>
Cc: kbuild-all@01.org, lkcamp@lists.libreplanetbr.org,
Helen Koike <helen.koike@collabora.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] media: vimc: vimc_pix_map_fmt_info() can be static
Date: Sun, 6 Oct 2019 08:28:05 +0800 [thread overview]
Message-ID: <20191006002805.i2gbquub7egjczhx@332d0cec05f4> (raw)
In-Reply-To: <20191005211136.552305-1-carlosecb@tutanota.com>
Fixes: 4d124d159dff ("media: vimc: get pixformat info from v4l2_format_info to avoid code repetition")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
vimc-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/vimc/vimc-common.c b/drivers/media/platform/vimc/vimc-common.c
index 9ea698810e1a1..c37442aba70b1 100644
--- a/drivers/media/platform/vimc/vimc-common.c
+++ b/drivers/media/platform/vimc/vimc-common.c
@@ -118,7 +118,7 @@ static struct vimc_pix_map_fmt vimc_pix_map_fmt_list[] = {
},
};
-struct vimc_pix_map vimc_pix_map_fmt_info(struct vimc_pix_map_fmt *vfmt)
+static struct vimc_pix_map vimc_pix_map_fmt_info(struct vimc_pix_map_fmt *vfmt)
{
struct vimc_pix_map vpix = {
next prev parent reply other threads:[~2019-10-06 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 21:11 [PATCH] media: vimc: get pixformat info from v4l2_format_info to avoid code repetition Carlos E. C. Barbosa
2019-10-06 0:28 ` kbuild test robot
2019-10-06 0:28 ` kbuild test robot [this message]
2019-10-06 1:36 ` [RFC PATCH] media: vimc: vimc_pix_map_fmt_info() can be static Helen Koike
2019-10-07 15:18 ` [Lkcamp] " André Almeida
2019-10-07 16:12 ` Helen Koike
2019-10-06 1:27 ` [PATCH] media: vimc: get pixformat info from v4l2_format_info to avoid code repetition Helen Koike
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=20191006002805.i2gbquub7egjczhx@332d0cec05f4 \
--to=lkp@intel.com \
--cc=climacobarbosacee@gmail.com \
--cc=helen.koike@collabora.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.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).