From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Michal Nazarewicz <mina86@mina86.com>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Borislav Petkov <bp@suse.de>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Johannes Berg <johannes.berg@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH v4 2/2] kernel.h: handle pointers to arrays better in container_of()
Date: Wed, 24 May 2017 11:59:16 -0700 [thread overview]
Message-ID: <20170524115916.4c7abeab29ddd73adc59f762@linux-foundation.org> (raw)
In-Reply-To: <7dbdfa72-e168-3b50-90dc-bca8239e8081@mev.co.uk>
On Wed, 24 May 2017 11:46:17 +0100 Ian Abbott <abbotti@mev.co.uk> wrote:
> This breakage occurs when <asm-generic/bug.h> is included before
> <include/linux.h> due to a circular dependancy I introduced with this
> commit.
>
> It can be fixed by replacing the `#include <linux/kernel.h>` with
> `#include <linux/types.h>` in "include/asm-generic/bug.h". I can send a
> patch to fix that, but ideally, it should be committed before this
> commit to avoid breakage during git bisect builds. So my question is,
> should I send a single patch to fix this breakage, or resend the series
> of patches to incorporate this fix before the current commit?
I expect a full resend would be best - that way the test robot should
be able to parse and retest it in the usual fashion.
prev parent reply other threads:[~2017-05-24 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 16:01 [PATCH v4 0/2] kernel.h: container_of() pointer checking Ian Abbott
2017-05-23 16:01 ` [PATCH v4 1/2] asm-generic/bug.h: declare struct pt_regs; before function prototype Ian Abbott
2017-05-23 18:44 ` Michal Nazarewicz
2017-05-23 16:01 ` [PATCH v4 2/2] kernel.h: handle pointers to arrays better in container_of() Ian Abbott
2017-05-23 18:44 ` Michal Nazarewicz
2017-05-24 0:54 ` kbuild test robot
2017-05-24 10:46 ` Ian Abbott
2017-05-24 18:59 ` Andrew Morton [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=20170524115916.4c7abeab29ddd73adc59f762@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=abbotti@mev.co.uk \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=glider@google.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=johannes.berg@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@intel.com \
--cc=mina86@mina86.com \
--cc=peterz@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
Powered by JetHome