From: Sven Eckelmann <sven@narfation.org>
To: Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
b.a.t.m.a.n@lists.open-mesh.org,
linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] asm-generic: avoid sparse {get,put}_unaligned warning
Date: Mon, 26 Jul 2021 17:04:46 +0200 [thread overview]
Message-ID: <3234493.RMHOAZ7QyG@ripper> (raw)
In-Reply-To: <CAK8P3a2MVQMFFBUzudy+yrcp4Md8mm=NcvX7YzGVz4C8W61sgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Monday, 26 July 2021 14:57:31 CEST Arnd Bergmann wrote:
> >
> > > The special attribute force must be used in such statements when the cast
> > > is known to be safe to avoid these warnings.
>
> I can see why this would warn, but I'm having trouble reproducing the
> warning on linux-next.
I have sparse 0.6.3 on an Debian bullseye amd64 system. Sources are from
linux-next next-20210723
make allnoconfig
cat >> .config << "EOF"
CONFIG_NET=y
CONFIG_INET=y
CONFIG_BATMAN_ADV=y
CONFIG_BATMAN_ADV_DAT=y
EOF
make olddefconfig
make CHECK="sparse -Wbitwise-pointer" C=1
I should maybe have made this clearer in the last sentence of the first
paragraph: "This is also true for pointers to variables with this type when
-Wbitwise-pointer is activated."
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-26 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 16:24 [PATCH] asm-generic: avoid sparse {get,put}_unaligned warning Sven Eckelmann
2021-07-24 17:01 ` Al Viro
2021-07-26 12:57 ` Arnd Bergmann
2021-07-26 15:04 ` Sven Eckelmann [this message]
2021-07-26 16:22 ` Arnd Bergmann
2021-07-27 8:44 ` David Laight
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=3234493.RMHOAZ7QyG@ripper \
--to=sven@narfation.org \
--cc=arnd@arndb.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.