From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: linuxppc <linuxppc-dev@lists.ozlabs.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] jump_label: factor out the base part of jump_label.h to a separate file
Date: Fri, 30 Aug 2013 18:37:33 +0200 [thread overview]
Message-ID: <20130830163732.GA2353@hpx.cz> (raw)
In-Reply-To: <1377414952-15995-2-git-send-email-haokexin@gmail.com>
2013-08-25 15:15+0800, Kevin Hao:
> We plan to use the jump label in the cpu/mmu feature check on ppc.
> This will need to include the jump_label.h in several very basic header
> files of ppc which seems to be included by most of the other head
> files implicitly or explicitly. But in the current jump_label.h,
> it also include the "linux/workqueue.h" and this will cause recursive
> inclusion. In order to fix this, we choose to factor out the base
> part of jump_label.h to a separate header file and we can include
> that file instead of jump_label.h to avoid the recursive inclusion.
> No functional change.
"linux/workqueue.h" was included because of deferred keys and they are
split into "linux/jump_label_ratelimit.h" to solve the same problem in
paravirt ticket spinlock series.
(still in -next: 851cf6e7 jump_label: Split jumplabel ratelimit)
next prev parent reply other threads:[~2013-08-30 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 7:15 [PATCH 0/5] powerpc: use jump label for cpu/mmu_has_feature Kevin Hao
2013-08-25 7:15 ` [PATCH 1/5] jump_label: factor out the base part of jump_label.h to a separate file Kevin Hao
2013-08-30 16:37 ` Radim Krčmář [this message]
2013-09-02 2:23 ` Kevin Hao
2013-08-25 7:15 ` [PATCH 2/5] jump_label: also include linux/atomic.h when jump label is enabled Kevin Hao
2013-08-25 7:15 ` [PATCH 3/5] powerpc: move the cpu_has_feature to a separate file Kevin Hao
2013-08-25 7:15 ` [PATCH 4/5] powerpc: use the jump label for cpu_has_feature Kevin Hao
2013-08-25 7:15 ` [PATCH 5/5] powerpc: use jump label for mmu_has_feature Kevin Hao
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=20130830163732.GA2353@hpx.cz \
--to=rkrcmar@redhat.com \
--cc=haokexin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).