mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Tiffany Lin <tiffany.lin@mediatek.com>
Cc: kbuild-all@01.org, Hans Verkuil <hans.verkuil@cisco.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Daniel Kurtz <djkurtz@chromium.org>,
	Pawel Osciak <posciak@chromium.org>,
	Eddie Huang <eddie.huang@mediatek.com>,
	Yingjoe Chen <yingjoe.chen@mediatek.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-mediatek@lists.infradead.org, Tiffany.lin@mediatek.com
Subject: Re: [PATCH v3] vcodec: mediatek: Add g/s_selection support for V4L2 Encoder
Date: Thu, 4 Aug 2016 20:12:28 +0800	[thread overview]
Message-ID: <201608042055.ZSTFBzp0%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470305295-27785-1-git-send-email-tiffany.lin@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

Hi Tiffany,

[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on next-20160804]
[cannot apply to v4.7]
[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/Tiffany-Lin/vcodec-mediatek-Add-g-s_selection-support-for-V4L2-Encoder/20160804-181402
base:   git://linuxtv.org/media_tree.git master
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c: In function 'vidioc_venc_s_selection':
>> drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c:680:9: error: implicit declaration of function 'v4l2_s_selection' [-Werror=implicit-function-declaration]
      err = v4l2_s_selection(s, &r);
            ^~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/v4l2_s_selection +680 drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c

   674		case V4L2_SEL_TGT_CROP:
   675			/* Only support crop from (0,0) */
   676			s->r.top = 0;
   677			s->r.left = 0;
   678			r.width = min(r.width, q_data->coded_width);
   679			r.height = min(r.height, q_data->coded_height);
 > 680			err = v4l2_s_selection(s, &r);
   681			if (err)
   682				return err;
   683			q_data->visible_width = s->r.width;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 55451 bytes --]

  reply	other threads:[~2016-08-04 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 10:08 Tiffany Lin
2016-08-04 12:12 ` kbuild test robot [this message]
2016-08-04 13:00 ` Hans Verkuil
2016-08-05  3:12   ` Tiffany Lin

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=201608042055.ZSTFBzp0%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=djkurtz@chromium.org \
    --cc=eddie.huang@mediatek.com \
    --cc=hans.verkuil@cisco.com \
    --cc=kbuild-all@01.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@osg.samsung.com \
    --cc=posciak@chromium.org \
    --cc=tiffany.lin@mediatek.com \
    --cc=yingjoe.chen@mediatek.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

all inboxes | Powered by JetHome®