From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] add helper predefine_{strong,weak}()
Date: Sun, 5 Jul 2020 15:16:02 +0200 [thread overview]
Message-ID: <20200705131605.26551-1-luc.vanoostenryck@gmail.com> (raw)
A lot of predefined macros are just set to the value '1'.
So, create a pair of helper for this and use it to limit
the use of add_pre_buffer() in target-specific files.
Luc Van Oostenryck (2):
predefine: add helper predefine_{strong,weak}()
predefine: avoid add_pre_buffer() for targets
lib.h | 2 ++
pre-process.c | 26 ++++++++++++++++++++++++++
target-arm64.c | 2 +-
target-riscv.c | 2 +-
4 files changed, 30 insertions(+), 2 deletions(-)
base-commit: 88c90bb192663bfc2dc54782c316e39e6fe26e1d
--
2.27.0
next reply other threads:[~2020-07-05 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 13:16 Luc Van Oostenryck [this message]
2020-07-05 13:16 ` [PATCH 1/2] predefine: add helper predefine_{strong,weak}() Luc Van Oostenryck
2020-07-05 13:16 ` [PATCH 2/2] predefine: avoid add_pre_buffer() for targets Luc Van Oostenryck
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=20200705131605.26551-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).