[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac59684b-37fc-4e47-b496-e6f9bac87b8c@intel.com>
Date: Mon, 7 Oct 2024 12:13:53 +0200
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: Markus Elfring <Markus.Elfring@....de>, <kernel-janitors@...r.kernel.org>
CC: LKML <linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>, "Andy
Shevchenko" <andriy.shevchenko@...el.com>,
Amadeusz Sławiński
<amadeuszx.slawinski@...ux.intel.com>, Dan Carpenter
<dan.carpenter@...aro.org>, Dmitry Torokhov <dmitry.torokhov@...il.com>,
"Kees Cook" <kees@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Tony
Nguyen <anthony.l.nguyen@...el.com>
Subject: Re: [PATCH v1] cleanup: adjust scoped_guard() to avoid potential
warning
On 10/3/24 18:00, Markus Elfring wrote:
>> …
>>
>>>> "__" prefix added to internal macros;
>>
>> …
>>
>>> Would you get into the mood to reconsider the usage of leading underscores
>>> any more for selected identifiers?
>>> https://wiki.sei.cmu.edu/confluence/display/c/DCL37-C.+Do+not+declare+or+define+a+reserved+identifier
>>
>> The mentioned URL doesn't cover the special cases like the kernels of the
>> operating systems or other quite low level code.
> Can such a view be clarified further according to available information?
>
> Regards,
> Markus
could you please update CMU SEI wiki to be relevant for kernel drivers
development, so future generations of C bureaucrats would not be fooled?
Powered by blists - more mailing lists