From: kbuild test robot <lkp@intel.com>
To: Rui Miguel Silva <rui.silva@linaro.org>
Cc: kbuild-all@01.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, hverkuil@xs4all.nl,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Ryan Harkin <ryan.harkin@linaro.org>,
Rui Miguel Silva <rui.silva@linaro.org>
Subject: Re: [PATCH v3 2/2] media: ov2680: Add Omnivision OV2680 sensor driver
Date: Thu, 15 Mar 2018 05:36:33 +0800 [thread overview]
Message-ID: <201803150517.wAzOCpMR%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180313113311.8617-3-rui.silva@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3251 bytes --]
Hi Rui,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
[cannot apply to next-20180314]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Rui-Miguel-Silva/media-Introduce-Omnivision-OV2680-driver/20180315-020617
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/media/i2c/ov2680.c: In function 'ov2680_set_fmt':
drivers/media/i2c/ov2680.c:713:9: error: implicit declaration of function 'v4l2_find_nearest_size'; did you mean 'v4l2_find_nearest_format'? [-Werror=implicit-function-declaration]
mode = v4l2_find_nearest_size(ov2680_mode_data,
^~~~~~~~~~~~~~~~~~~~~~
v4l2_find_nearest_format
drivers/media/i2c/ov2680.c:714:195: error: 'width' undeclared (first use in this function)
ARRAY_SIZE(ov2680_mode_data), width,
^
drivers/media/i2c/ov2680.c:714:195: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/media/i2c/ov2680.c:715:11: error: 'height' undeclared (first use in this function); did you mean '__iget'?
height, fmt->width, fmt->height);
^~~~~~
__iget
cc1: some warnings being treated as errors
vim +715 drivers/media/i2c/ov2680.c
693
694 static int ov2680_set_fmt(struct v4l2_subdev *sd,
695 struct v4l2_subdev_pad_config *cfg,
696 struct v4l2_subdev_format *format)
697 {
698 struct ov2680_dev *sensor = to_ov2680_dev(sd);
699 struct v4l2_mbus_framefmt *fmt = &format->format;
700 const struct ov2680_mode_info *mode;
701 int ret = 0;
702
703 if (format->pad != 0)
704 return -EINVAL;
705
706 mutex_lock(&sensor->lock);
707
708 if (sensor->is_streaming) {
709 ret = -EBUSY;
710 goto unlock;
711 }
712
> 713 mode = v4l2_find_nearest_size(ov2680_mode_data,
714 ARRAY_SIZE(ov2680_mode_data), width,
> 715 height, fmt->width, fmt->height);
716 if (!mode) {
717 ret = -EINVAL;
718 goto unlock;
719 }
720
721 if (format->which == V4L2_SUBDEV_FORMAT_TRY) {
722 fmt = v4l2_subdev_get_try_format(sd, cfg, 0);
723
724 *fmt = format->format;
725 goto unlock;
726 }
727
728 fmt->width = mode->width;
729 fmt->height = mode->height;
730 fmt->code = sensor->fmt.code;
731 fmt->colorspace = sensor->fmt.colorspace;
732
733 sensor->current_mode = mode;
734 sensor->fmt = format->format;
735 sensor->mode_pending_changes = true;
736
737 unlock:
738 mutex_unlock(&sensor->lock);
739
740 return ret;
741 }
742
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62379 bytes --]
next prev parent reply other threads:[~2018-03-14 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 11:33 [PATCH v3 0/2] media: Introduce Omnivision OV2680 driver Rui Miguel Silva
2018-03-13 11:33 ` [PATCH v3 1/2] media: ov2680: dt: Add bindings for OV2680 Rui Miguel Silva
2018-03-13 11:33 ` [PATCH v3 2/2] media: ov2680: Add Omnivision OV2680 sensor driver Rui Miguel Silva
2018-03-14 19:39 ` kbuild test robot
2018-03-15 9:29 ` Rui Miguel Silva
2018-03-16 16:10 ` Sakari Ailus
2018-03-16 16:51 ` Rui Miguel Silva
2018-03-14 21:36 ` kbuild test robot [this message]
2018-03-24 10:57 ` Sakari Ailus
2018-03-27 12:39 ` Rui Miguel Silva
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=201803150517.wAzOCpMR%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rui.silva@linaro.org \
--cc=ryan.harkin@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome