From: Ian Abbott <abbotti@mev.co.uk>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
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: [PATCH 0/1] bug: fix problem including <linux.bug.h> from linux/kernel.h
Date: Wed, 24 May 2017 14:21:06 +0100 [thread overview]
Message-ID: <20170524132107.6919-1-abbotti@mev.co.uk> (raw)
PATCH 1 is a follow-up patch to my previous patch "[PATCH v4 2/2]
kernel.h: handle pointers to arrays better in container_of()":
<https://lkml.org/lkml/2017/5/23/641>. The previous patch introduced a
build failure:
<https://lists.01.org/pipermail/kbuild-all/2017-May/034127.html>. The
build failure was due to a circular dependency introduced by the
previous patch and occurs when <asm-generic/bug.h> is included before
<linux/kernel.h> for architectures that select `CONFIG_GENERIC_BUG`.
PATCH 1 fixes this circular dependency. Ideally, it should be applied
before my previous patch to avoid breakage during git bisect builds, but
can be applied after if that is not a concern.
1) bug: fix problem including <linux.bug.h> from linux/kernel.h
include/asm-generic/bug.h | 1 -
include/linux/bug.h | 1 +
2 files changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2017-05-24 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 13:21 Ian Abbott [this message]
2017-05-24 13:21 ` [PATCH 1/1] " Ian Abbott
2017-05-24 13:37 ` Rasmus Villemoes
2017-05-24 15:55 ` Ian Abbott
2017-05-24 16:06 ` [PATCH v2] bug: fix problem including <linux/bug.h> " Ian Abbott
2017-05-24 23:11 ` Ian Abbott
2017-05-24 23:26 ` kbuild test robot
2017-05-24 23:53 ` kbuild test robot
2017-05-25 2:25 ` [PATCH 1/1] bug: fix problem including <linux.bug.h> " kbuild test robot
2017-05-25 2:47 ` kbuild test robot
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=20170524132107.6919-1-abbotti@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=glider@google.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=johannes.berg@intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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
all inboxes | Powered by JetHome®