[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWBBFS1HZGoaixakFEOTPyWtp6dsOeYi3UFNKT7f00a3w@mail.gmail.com>
Date: Mon, 5 Dec 2016 18:48:06 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Sebastian Frias <sf84@...oste.net>
Cc: zijun_hu <zijun_hu@....com>, Sasha Levin <sasha.levin@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Mason <slash.tmp@...e.fr>,
Maxime Coquelin <maxime.coquelin@...com>,
Harvey Harrison <harvey.harrison@...il.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH] bitops: add equivalent of BIT(x) for bitfields
On Mon, Dec 5, 2016 at 2:36 PM, Sebastian Frias <sf84@...oste.net> wrote:
> Introduce SETBITFIELD(msb, lsb, value) macro to ease dealing with
> continuous bitfields, just as BIT(x) does for single bits.
If it's a bitfield, why not calling it that way?
So what about BITFIELD(start ,size), like arch/tile/kernel/tile-desc_32.c has?
> SETBITFIELD_ULL(msb, lsb, value) macro is also added.
Confused by the need for a "value" parameter...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists