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: Re: [PATCH] media: vimc: get pixformat info from v4l2_format_info to avoid code repetition
Date: Sun, 6 Oct 2019 08:28:02 +0800 [thread overview]
Message-ID: <201910060859.oiVSDnT0%lkp@intel.com> (raw)
In-Reply-To: <20191005211136.552305-1-carlosecb@tutanota.com>
Hi "Carlos,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[cannot apply to v5.4-rc1 next-20191004]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Carlos-E-C-Barbosa/media-vimc-get-pixformat-info-from-v4l2_format_info-to-avoid-code-repetition/20191006-053120
base: git://linuxtv.org/media_tree.git master
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-42-g38eda53-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/media/platform/vimc/vimc-common.c:121:21: sparse: sparse: symbol 'vimc_pix_map_fmt_info' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-10-06 0:29 UTC|newest]
Thread overview: 10+ 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 [this message]
2019-10-06 0:28 ` [RFC PATCH] media: vimc: vimc_pix_map_fmt_info() can be static kbuild test robot
2019-10-06 1:36 ` 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
-- strict thread matches above, loose matches on Subject: below --
2019-10-15 22:52 Carlos E. C. Barbosa
2019-12-13 10:09 ` Hans Verkuil
2019-12-18 13:43 ` 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=201910060859.oiVSDnT0%lkp@intel.com \
--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