From: Markus Elfring <Markus.Elfring@web.de>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Kees Cook" <kees@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>
Subject: Re: cleanup: adjust scoped_guard() to avoid potential warning
Date: Mon, 7 Oct 2024 12:46:55 +0200 [thread overview]
Message-ID: <f5296465-b160-4cb7-9a19-7cabd100e7a1@web.de> (raw)
In-Reply-To: <ac59684b-37fc-4e47-b496-e6f9bac87b8c@intel.com>
>>>> 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?
…
> could you please update CMU SEI wiki to be relevant for kernel drivers
> development, so future generations of C bureaucrats would not be fooled?
How do you disagree to mentioned technical aspects?
Regards,
Markus
next prev parent reply other threads:[~2024-10-07 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 11:39 [PATCH v1] " Przemek Kitszel
2024-10-03 12:34 ` Markus Elfring
2024-10-03 12:44 ` Andy Shevchenko
2024-10-03 16:00 ` Markus Elfring
2024-10-07 10:13 ` Przemek Kitszel
2024-10-07 10:46 ` Markus Elfring [this message]
2024-10-03 12:43 ` Andy Shevchenko
2024-10-03 12:46 ` Andy Shevchenko
2024-10-03 13:38 ` Przemek Kitszel
2024-10-03 17:47 ` Andy Shevchenko
2024-10-03 14:12 ` Peter Zijlstra
2024-10-03 17:51 ` Andy Shevchenko
2024-10-04 9:33 ` Peter Zijlstra
2024-10-04 13:52 ` Andy Shevchenko
2024-10-03 13:00 ` Dmitry Torokhov
2024-10-03 13:42 ` Przemek Kitszel
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=f5296465-b160-4cb7-9a19-7cabd100e7a1@web.de \
--to=markus.elfring@web.de \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dan.carpenter@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=przemyslaw.kitszel@intel.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
Powered by JetHome