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,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Simon Horman" <horms@kernel.org>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [RFC] cleanup: make scoped_guard() to be return-friendly
Date: Mon, 30 Sep 2024 14:51:43 +0200 [thread overview]
Message-ID: <3f4228f2-3ad5-4491-8236-6a7fbc5274ff@web.de> (raw)
In-Reply-To: <34d2f916-3551-4b75-b87a-9d413662369b@intel.com>
>> * Would you ever like to avoid reserved identifiers in such source code?
>> https://wiki.sei.cmu.edu/confluence/display/c/DCL37-C.+Do+not+declare+or+define+a+reserved+identifier
>
> we already don't care about this guideline (see __guard_ptr())
Please take another look at name conventions.
How do you think about to avoid that this software depends on undefined behaviour?
Regards,
Markus
prev parent reply other threads:[~2024-09-30 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:41 [RFC PATCH] cleanup: make scoped_guard() to be return-friendly Przemek Kitszel
2024-09-27 7:31 ` Dan Carpenter
2024-09-27 14:08 ` Przemek Kitszel
2024-09-27 15:04 ` Dan Carpenter
2024-09-30 10:21 ` Przemek Kitszel
2024-09-30 11:08 ` Dan Carpenter
2024-09-30 11:30 ` Przemek Kitszel
2024-09-30 12:57 ` Dan Carpenter
2024-09-30 13:07 ` Dmitry Torokhov
2024-09-30 12:57 ` Dmitry Torokhov
2024-09-30 11:30 ` Markus Elfring
2024-09-30 12:33 ` Przemek Kitszel
2024-09-30 12:51 ` Markus Elfring [this message]
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=3f4228f2-3ad5-4491-8236-6a7fbc5274ff@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=horms@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