Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Stephen Smalley" <stephen.smalley.work@gmail.com>,
	"Ondrej Mosnacek" <omosnace@redhat.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	linux-kbuild@vger.kernel.org, selinux@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH v2] selinux: add generated av_permissions.h to targets
Date: Wed, 11 Dec 2024 13:42:33 -0500	[thread overview]
Message-ID: <e9fa92d65ef886d1f5ac8daf1bbc3939@paul-moore.com> (raw)
In-Reply-To: <20241127-selinux-clean-v2-1-a6e528c1ff93@linutronix.de>

On Nov 27, 2024 =?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de> wrote:
> 
> av_permissions.h was not declared as a target and therefore not cleaned
> up automatically by kbuild.
> 
> Suggested-by: Masahiro Yamada <masahiroy@kernel.org>
> Link: https://lore.kernel.org/lkml/CAK7LNATUnCPt03BRFSKh1EH=+Sy0Q48wE4ER0BZdJqOb_44L8w@mail.gmail.com/
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> Changes in v2:
> - Adopt Masahiro's suggestion
> - Link to v1: https://lore.kernel.org/r/20241120-selinux-clean-v1-1-68704e007f7a@linutronix.de
> ---
> I left out the modifications to the grouped target comments.
> The current state doesn't hurt and I was not able to come up with
> something actually nice.
> ---
>  security/selinux/Makefile | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)

Looks good to me, merging into selinux/dev.  Thanks everyone!

--
paul-moore.com

      parent reply	other threads:[~2024-12-11 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 10:09 [PATCH v2] selinux: add generated av_permissions.h to targets Thomas Weißschuh
2024-11-27 23:53 ` Masahiro Yamada
2024-12-11 18:42 ` Paul Moore [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=e9fa92d65ef886d1f5ac8daf1bbc3939@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=omosnace@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    --cc=thomas.weissschuh@linutronix.de \
    /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