From: Valdis.Kletnieks@vt.edu
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Christoph Lameter <cl@linux.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: slab.h debugging tags....
Date: Sat, 10 Oct 2015 14:34:31 -0400 [thread overview]
Message-ID: <131236.1444502071@turing-police.cc.vt.edu> (raw)
In-Reply-To: <87pp0n96fi.fsf@rasmusvillemoes.dk>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Fri, 09 Oct 2015 21:40:33 +0200, Rasmus Villemoes said:
> Does this fix it for you?
>
> Subject: [PATCH] slab.h: hide assume_aligned attribute from sparse
>
> sparse apparently pretends to be gcc >= 4.9, yet isn't prepared to
Much better - it threw messages on a few files, it took me a moment to figure
out what happened.
CHECK init/do_mounts_initrd.c
init/do_mounts_initrd.c:8:2: warning: "Sparse checking disabled for this file"
include/linux/slab.h:307:43: error: attribute '__assume_aligned__': unknown attribute
include/linux/slab.h:308:58: error: attribute '__assume_aligned__': unknown attribute
include/linux/slab.h:337:73: error: attribute '__assume_aligned__': unknown attribute
include/linux/slab.h:375:74: error: attribute '__assume_aligned__': unknown attribute
include/linux/slab.h:378:80: error: attribute '__assume_aligned__': unknown attribute
but there's only like a few that disable sparse. Everything else behaves now.
Feel free to stick this on it:
Tested-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
prev parent reply other threads:[~2015-10-10 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 0:12 Valdis Kletnieks
2015-10-09 19:40 ` Rasmus Villemoes
2015-10-10 18:34 ` Valdis.Kletnieks [this message]
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=131236.1444502071@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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®