Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Ba Jing <bajing@cmss.chinamobile.com>, Jeff Xu <jeffxu@google.com>
Cc: gnoack@google.com, shuah@kernel.org,
	 linux-security-module@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] landlock: ptrace_test: remove unused macros
Date: Fri, 10 Jan 2025 12:23:12 +0100	[thread overview]
Message-ID: <20250110.do3boi0AeKee@digikod.net> (raw)
In-Reply-To: <20241118042407.12900-1-bajing@cmss.chinamobile.com>

Thanks!  This is now merged in my next tree.

On Mon, Nov 18, 2024 at 12:24:07PM +0800, Ba Jing wrote:
> After reviewing the code, it was found that these macros are never
> referenced in the code. Just remove them.
> 
> Signed-off-by: Ba Jing <bajing@cmss.chinamobile.com>
> ---
>  tools/testing/selftests/landlock/ptrace_test.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/landlock/ptrace_test.c b/tools/testing/selftests/landlock/ptrace_test.c
> index a19db4d0b3bd..8f31b673ff2d 100644
> --- a/tools/testing/selftests/landlock/ptrace_test.c
> +++ b/tools/testing/selftests/landlock/ptrace_test.c
> @@ -22,8 +22,6 @@
>  /* Copied from security/yama/yama_lsm.c */
>  #define YAMA_SCOPE_DISABLED 0
>  #define YAMA_SCOPE_RELATIONAL 1
> -#define YAMA_SCOPE_CAPABILITY 2
> -#define YAMA_SCOPE_NO_ATTACH 3
>  
>  static void create_domain(struct __test_metadata *const _metadata)
>  {
> -- 
> 2.33.0
> 
> 
> 
> 

      reply	other threads:[~2025-01-10 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  4:24 [PATCH] landlock: ptrace_test: remove unused macros Ba Jing
2025-01-10 11:23 ` Mickaël Salaün [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=20250110.do3boi0AeKee@digikod.net \
    --to=mic@digikod.net \
    --cc=bajing@cmss.chinamobile.com \
    --cc=gnoack@google.com \
    --cc=jeffxu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=shuah@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