[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200324062853.GD1977781@kroah.com>
Date: Tue, 24 Mar 2020 07:28:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Eugene Syromiatnikov <esyr@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com,
Pratik Patel <pratikp@...eaurora.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
Michael Williams <michael.williams@....com>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Chunyan Zhang <zhang.chunyan@...aro.org>,
"Dmitry V. Levin" <ldv@...linux.org>
Subject: Re: [PATCH] coresight: do not use the BIT() macro in the UAPI header
On Tue, Mar 24, 2020 at 05:22:13AM +0100, Eugene Syromiatnikov wrote:
> The BIT() macro definition is not available for the UAPI headers
> (moreover, it can be defined differently in the user space); replace
> its usage with the _BITUL() macro that is defined in <linux/const.h>.
Why is somehow _BITUL() ok to use here instead?
Just open-code it, I didn't think we could use any BIT()-like macros in
uapi .h files.
thanks,
greg k-h
Powered by blists - more mailing lists