[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E607265CB020454880711A6F96C05A030106863C3E@hasmsx107.ger.corp.intel.com>
Date: Mon, 22 May 2017 09:58:01 +0000
From: "Levy, Amir (Jer)" <amir.jer.levy@...el.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andreas Noever <andreas.noever@...il.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Jamet, Michael" <michael.jamet@...el.com>,
"Bernat, Yehezkel" <yehezkel.bernat@...el.com>,
Lukas Wunner <lukas@...ner.de>,
Andy Lutomirski <luto@...nel.org>,
"Mario.Limonciello@...l.com" <Mario.Limonciello@...l.com>,
"Jared.Dominguez@...l.com" <Jared.Dominguez@...l.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 05/24] thunderbolt: Rework capability handling
On Mon, May 22 2017, 12:45 PM, Mika Westerberg wrote:
> I'm not sure it is good idea to use bit fields here at all. I'm not an expert in C
> but I remember reading somewhere that they are not suitable for representing
> fields inside hardware registers.
>
http://yarchive.net/comp/linux/bitfields.html
Powered by blists - more mailing lists