From: "Tom Schwindl" <schwindl@posteo.de>
To: <dash@vger.kernel.org>
Subject: STATIC vs static
Date: Fri, 17 Feb 2023 13:35:37 +0000 [thread overview]
Message-ID: <CQKVLXJRDK3X.124XXVEY9RH6K@morphine> (raw)
Hi all,
as I was skimming through the codebase, I noticed that sometimes there is a
macro, STATIC, used to represent the normal static. Is there a reason for that
or would a s/STATIC/static/g be welcome? Now that we are revising the prototypes
anyway I think it's the right time to bring this up.
--
Best Regards,
Tom Schwindl
next reply other threads:[~2023-02-17 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 13:35 Tom Schwindl [this message]
2023-02-20 9:04 ` STATIC vs static Herbert Xu
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=CQKVLXJRDK3X.124XXVEY9RH6K@morphine \
--to=schwindl@posteo.de \
--cc=dash@vger.kernel.org \
/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