From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: jgross@suse.com, xen-devel@lists.xensource.com, x86@kernel.org,
ryabinin.a.a@gmail.com, long.wanglong@huawei.com,
joro@8bytes.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, mcb30@ipxe.org,
luto@amacapital.net, aryabinin@virtuozzo.com, mingo@redhat.com,
bp@alien8.de, JBeulich@suse.com, hpa@zytor.com,
qiuxishi@huawei.com, tglx@linutronix.de,
boris.ostrovsky@oracle.com, mchehab@osg.samsung.com
Subject: Re: [PATCH v2] x86/boot: add BIT() to boot/bitops.h
Date: Fri, 12 Feb 2016 16:26:29 -0500 [thread overview]
Message-ID: <20160212212629.GC21514@char.us.oracle.com> (raw)
In-Reply-To: <1454734175-15328-1-git-send-email-mcgrof@kernel.org>
On Fri, Feb 05, 2016 at 08:49:35PM -0800, Luis R. Rodriguez wrote:
> The boot/bitops.h has guards against including the
> regular bitops (include/asm-generic/bitops.h), it only
> implements what we need at early boot. We'll be making
> use of BIT() later so add it.
>
> Users of boot/boot.h must include it prior to asm/setup.h
> otherwise the guard protection devised against the regular
> linux/bitops.h will not take effect.
>
> v2: spelling fixes, and language descriptipon enhancements
<laughs> descriptioioppnipoio ? :-)
> by Konrad.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
>
> This patch is originally part of a much larger series [0],
> this is v2 of the original patch 3/8 [1]. I've split this single
> patch out on its own now that it should be clear how I intend
> on using BIT() on early code.
>
> [0] http://lkml.kernel.org/r/1450217797-19295-1-git-send-email-mcgrof@do-not-panic.com
> [1] http://lkml.kernel.org/r/1450217797-19295-4-git-send-email-mcgrof@do-not-panic.com
>
> arch/x86/boot/bitops.h | 2 ++
> arch/x86/boot/boot.h | 2 +-
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/boot/bitops.h b/arch/x86/boot/bitops.h
> index 878e4b9940d9..232cff0ff4e3 100644
> --- a/arch/x86/boot/bitops.h
> +++ b/arch/x86/boot/bitops.h
> @@ -40,4 +40,6 @@ static inline void set_bit(int nr, void *addr)
> asm("btsl %1,%0" : "+m" (*(u32 *)addr) : "Ir" (nr));
> }
>
> +#define BIT(x) (1 << x)
> +
> #endif /* BOOT_BITOPS_H */
> diff --git a/arch/x86/boot/boot.h b/arch/x86/boot/boot.h
> index 9011a88353de..4fb53da1f48a 100644
> --- a/arch/x86/boot/boot.h
> +++ b/arch/x86/boot/boot.h
> @@ -23,8 +23,8 @@
> #include <stdarg.h>
> #include <linux/types.h>
> #include <linux/edd.h>
> -#include <asm/setup.h>
> #include "bitops.h"
> +#include <asm/setup.h>
> #include "ctype.h"
> #include "cpuflags.h"
>
> --
> 2.7.0
>
prev parent reply other threads:[~2016-02-12 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 4:49 [PATCH v2] x86/boot: add BIT() to boot/bitops.h Luis R. Rodriguez
2016-02-12 21:26 ` Konrad Rzeszutek Wilk [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=20160212212629.GC21514@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=aryabinin@virtuozzo.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=long.wanglong@huawei.com \
--cc=luto@amacapital.net \
--cc=mcb30@ipxe.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mingo@redhat.com \
--cc=qiuxishi@huawei.com \
--cc=rusty@rustcorp.com.au \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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).