From: Tejun Heo <tj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Qais Yousef <qais.yousef@imgtec.com>,
Alex Smith <alex.smith@imgtec.com>,
Markos Chandras <Markos.Chandras@imgtec.com>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: Build regressions/improvements in v4.4-rc7
Date: Mon, 28 Dec 2015 11:29:33 -0500 [thread overview]
Message-ID: <20151228162933.GV5003@mtj.duckdns.org> (raw)
In-Reply-To: <568161BC.3060208@infradead.org>
Hello,
On Mon, Dec 28, 2015 at 08:22:20AM -0800, Randy Dunlap wrote:
> On 12/28/15 08:18, Tejun Heo wrote:
> > On Mon, Dec 28, 2015 at 01:29:18PM +0100, Geert Uytterhoeven wrote:
> >> On Mon, Dec 28, 2015 at 1:21 PM, Geert Uytterhoeven
> >> <geert@linux-m68k.org> wrote:
> >>> JFYI, when comparing v4.4-rc7[1] to v4.4-rc6[3], the summaries are:
> >>> - build errors: +14/-3
> >>
> >> + /home/kisskb/slave/src/include/linux/kqueue.h: error:
> >> dereferencing type-punned pointer will break strict-aliasing rules
> >> [-Werror=strict-aliasing]: => 186:2
> >
> > kqueue.h?
> >
>
> + /home/kisskb/slave/src/include/linux/workqueue.h: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]: => 186:2
Heh, yeah, that makes a lot more sense. At the same time tho, the
code has been there forever and there are a lot of simliar derefs
throughout kernel/workqueue.c. Is there something the code should be
doing?
Thanks.
--
tejun
prev parent reply other threads:[~2015-12-28 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 12:21 Build regressions/improvements in v4.4-rc7 Geert Uytterhoeven
2015-12-28 12:29 ` Geert Uytterhoeven
2015-12-28 16:18 ` Tejun Heo
2015-12-28 16:22 ` Randy Dunlap
2015-12-28 16:29 ` Tejun Heo [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=20151228162933.GV5003@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=Markos.Chandras@imgtec.com \
--cc=alex.smith@imgtec.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=qais.yousef@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=rdunlap@infradead.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