From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Mark Salyzyn <salyzyn@android.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: linux-next - sparse warnings after prefered/preferred patch.
Date: Thu, 24 Oct 2019 00:19:44 -0400 [thread overview]
Message-ID: <822877.1571890784@turing-police> (raw)
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Building with C=1 W=1. After this commit:
commit 79f0cf35dccb1df27436c11b1a928b7a46152211
Author: Mark Salyzyn <salyzyn@android.com>
Date: Wed Oct 23 11:25:16 2019 +1100
treewide: cleanup: replace prefered with preferred
sparse throws messages on every single .c that includes sysctl.h:
CHECK kernel/sched/wait.c
./include/uapi/linux/sysctl.h:561:36: error: Expected } at end of specifier
./include/uapi/linux/sysctl.h:561:36: error: got __attribute__
CC kernel/sched/wait.o
CHECK kernel/sched/wait_bit.c
./include/uapi/linux/sysctl.h:561:36: error: Expected } at end of specifier
./include/uapi/linux/sysctl.h:561:36: error: got __attribute__
CC kernel/sched/wait_bit.o
CHECK kernel/sched/swait.c
./include/uapi/linux/sysctl.h:561:36: error: Expected } at end of specifier
./include/uapi/linux/sysctl.h:561:36: error: got __attribute__
CC kernel/sched/swait.o
The build has only gotten through 471 CC's so far - and 327 have thrown warnings.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-10-24 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 4:19 Valdis Klētnieks [this message]
2019-10-24 5:35 ` linux-next - sparse warnings after prefered/preferred patch Stephen Rothwell
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=822877.1571890784@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salyzyn@android.com \
--cc=sfr@canb.auug.org.au \
/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