From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Federico Simoncelli <fsimonce@redhat.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, kbuild-all@01.org
Subject: Re: [linuxtv-media:master 499/499] drivers/media/usb/usbtv/usbtv-core.c:119:22: sparse: symbol 'usbtv_id_table' was not declared. Should it be static?
Date: Wed, 05 Mar 2014 14:27:46 -0300 [thread overview]
Message-ID: <20140305142746.4ef16bff@samsung.com> (raw)
In-Reply-To: <52f0ac8a.aIXONk2PY1rBXEn8%fengguang.wu@intel.com>
Hi Fengguang,
This patch got obsoleted by another patch in the same series.
Unfortunately, I had to break sending the patch series into a few
pushes, as my mailbomb script has a logic there that prevents it to
send more than 30~50 emails (I never remember the exact setting).
So, I pushed this 80-series into a few pushes. You likely compiled the
tree without waiting for the hole series to be upstreamed.
Regards,
Mauro
Em Tue, 04 Feb 2014 17:02:02 +0800
kbuild test robot <fengguang.wu@intel.com> escreveu:
> tree: git://linuxtv.org/media_tree.git master
> head: a3550ea665acd1922df8275379028c1634675629
> commit: a3550ea665acd1922df8275379028c1634675629 [499/499] [media] usbtv: split core and video implementation
> reproduce: make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
> >> drivers/media/usb/usbtv/usbtv-core.c:119:22: sparse: symbol 'usbtv_id_table' was not declared. Should it be static?
> >> drivers/media/usb/usbtv/usbtv-core.c:129:19: sparse: symbol 'usbtv_usb_driver' was not declared. Should it be static?
> --
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:285:14: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:287:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:288:15: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:289:20: sparse: cast to restricted __be32
> >> drivers/media/usb/usbtv/usbtv-video.c:565:23: sparse: symbol 'usbtv_ioctl_ops' was not declared. Should it be static?
> >> drivers/media/usb/usbtv/usbtv-video.c:587:29: sparse: symbol 'usbtv_fops' was not declared. Should it be static?
> >> drivers/media/usb/usbtv/usbtv-video.c:648:16: sparse: symbol 'usbtv_vb2_ops' was not declared. Should it be static?
>
> Please consider folding the attached diff :-)
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
Cheers,
Mauro
next prev parent reply other threads:[~2014-03-05 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 9:02 [linuxtv-media:master 499/499] drivers/media/usb/usbtv/usbtv-core.c:119:22: sparse: symbol 'usbtv_id_table' was not declared. Should it be static? kbuild test robot
2014-03-05 17:27 ` Mauro Carvalho Chehab [this message]
2014-03-05 20:31 ` Mauro Carvalho Chehab
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=20140305142746.4ef16bff@samsung.com \
--to=m.chehab@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=fsimonce@redhat.com \
--cc=hans.verkuil@cisco.com \
--cc=kbuild-all@01.org \
--cc=linux-media@vger.kernel.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