From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Andy Walls <awalls@md.metrocast.net>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
llvm@lists.linux.dev
Subject: [PATCH 00/10] Address some clang W=1 warnings
Date: Mon, 22 Nov 2021 09:26:02 +0000 [thread overview]
Message-ID: <cover.1637573097.git.mchehab+huawei@kernel.org> (raw)
Clang is more pedantic than gcc with W=1. This is currently causing
builder.linuxtv.org errors due to CONFIG_WERROR.
Address some of those.
Mauro Carvalho Chehab (10):
media: cx25821: drop duplicated i2c_slave_did_ack()
media: ivtv: drop an unused macro
media: cx18: drop an unused macro
media: stb6100: mark a currently unused function as such
media: mc: mark a debug function with __maybe_unused
media: dvb-core: dvb_frontend: address some clang warnings
media: cx25840: drop some unused inline functions
media: marvell-ccic: drop to_cam() unused function
media: omap3isp: mark isp_isr_dbg as __maybe_unused
media: omap3isp: avoid warnings at IS_OUT_OF_BOUNDS()
drivers/media/dvb-core/dvb_frontend.c | 13 +++++-------
drivers/media/dvb-frontends/stb6100.c | 2 +-
drivers/media/i2c/cx25840/cx25840-ir.c | 20 -------------------
drivers/media/mc/mc-entity.c | 2 +-
drivers/media/pci/cx18/cx18-alsa-main.c | 6 ------
drivers/media/pci/cx25821/cx25821-core.c | 7 -------
drivers/media/pci/ivtv/ivtv-alsa-main.c | 6 ------
.../media/platform/marvell-ccic/cafe-driver.c | 7 -------
drivers/media/platform/omap3isp/isp.c | 3 ++-
drivers/media/platform/omap3isp/isph3a_af.c | 2 +-
10 files changed, 10 insertions(+), 58 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-22 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 9:26 Mauro Carvalho Chehab [this message]
2021-11-22 9:26 ` [PATCH 01/10] media: cx25821: drop duplicated i2c_slave_did_ack() Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 02/10] media: ivtv: drop an unused macro Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 03/10] media: cx18: " Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 04/10] media: stb6100: mark a currently unused function as such Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 05/10] media: mc: mark a debug function with __maybe_unused Mauro Carvalho Chehab
2021-11-22 9:57 ` Laurent Pinchart
2021-11-22 9:26 ` [PATCH 06/10] media: dvb-core: dvb_frontend: address some clang warnings Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 07/10] media: cx25840: drop some unused inline functions Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 08/10] media: marvell-ccic: drop to_cam() unused function Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 09/10] media: omap3isp: mark isp_isr_dbg as __maybe_unused Mauro Carvalho Chehab
2021-11-22 9:58 ` Laurent Pinchart
2021-11-29 7:58 ` [PATCH v2 09/10] media: mc: drop an unused debug function Mauro Carvalho Chehab
2021-11-22 9:26 ` [PATCH 10/10] media: omap3isp: avoid warnings at IS_OUT_OF_BOUNDS() Mauro Carvalho Chehab
2021-11-22 10:04 ` Laurent Pinchart
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=cover.1637573097.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=awalls@md.metrocast.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=llvm@lists.linux.dev \
--cc=mauro.chehab@huawei.com \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).