mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/2] Define is_signed_type() once
Date: Fri, 26 Aug 2022 09:21:14 -0700	[thread overview]
Message-ID: <20220826162116.1050972-1-bvanassche@acm.org> (raw)

Hi Kees,

The changes in this patch series are as follows:
- Add a unit test for the is_signed_type() macro.
- Define the is_signed_type() macro once.

Please consider these patches for the next merge window.

Thanks,

Bart.

Bart Van Assche (2):
  testing/selftests: Add tests for the is_signed_type() macro
  overflow, tracing: Define the is_signed_type() macro once

 include/linux/compiler.h     |  6 +++++
 include/linux/overflow.h     |  1 -
 include/linux/trace_events.h |  2 --
 lib/Kconfig.debug            | 12 +++++++++
 lib/Makefile                 |  1 +
 lib/is_signed_type_test.c    | 48 ++++++++++++++++++++++++++++++++++++
 6 files changed, 67 insertions(+), 3 deletions(-)
 create mode 100644 lib/is_signed_type_test.c


             reply	other threads:[~2022-08-26 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 16:21 Bart Van Assche [this message]
2022-08-26 16:21 ` [PATCH 1/2] testing/selftests: Add tests for the is_signed_type() macro Bart Van Assche
2022-08-29 19:30   ` Kees Cook
2022-08-30  2:33   ` Isabella Basso
2022-08-30  3:30     ` Bart Van Assche
2022-08-31 17:53       ` Kees Cook
2022-08-30  9:41   ` Rasmus Villemoes
2022-09-06 22:42     ` Bart Van Assche
2022-09-06 22:48       ` Rasmus Villemoes
2022-08-26 16:21 ` [PATCH 2/2] overflow, tracing: Define the is_signed_type() macro once Bart Van Assche
2022-08-29 19:30   ` Kees Cook
2022-08-29 19:36 ` [PATCH 0/2] Define is_signed_type() once Kees Cook

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=20220826162116.1050972-1-bvanassche@acm.org \
    --to=bvanassche@acm.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®