All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fortify: fix various issues in test_fortify Makefile
Date: Mon, 15 Jul 2024 09:07:36 -0700	[thread overview]
Message-ID: <202407150905.56BBE11@keescook> (raw)
In-Reply-To: <20240715144529.101634-1-masahiroy@kernel.org>

On Mon, Jul 15, 2024 at 11:45:22PM +0900, Masahiro Yamada wrote:
> Applicable to v6.10 tag.
> 
> 
> 
> Masahiro Yamada (3):
>   fortify: use if_changed_dep to record header dependency in *.cmd files
>   fortify: refactor test_fortify Makefile to fix some build problems
>   fortify: move test_fortify.sh to lib/test_fortify/

Thanks for this improvement! I will take this into the hardening tree
after -rc2, unless you would prefer to send this during the merge window
based on your tree? (The fix you sent for the v6.10 release means my
trees based on -rc2 can't apply this series...)

-Kees

-- 
Kees Cook

  parent reply	other threads:[~2024-07-15 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 14:45 [PATCH 0/3] fortify: fix various issues in test_fortify Makefile Masahiro Yamada
2024-07-15 14:45 ` [PATCH 1/3] fortify: use if_changed_dep to record header dependency in *.cmd files Masahiro Yamada
2024-07-16 17:50   ` kernel test robot
2024-07-17  4:46     ` Masahiro Yamada
2024-07-17 22:19       ` Kees Cook
2024-07-18  4:22         ` Masahiro Yamada
2024-07-15 14:45 ` [PATCH 2/3] fortify: refactor test_fortify Makefile to fix some build problems Masahiro Yamada
2024-07-15 14:45 ` [PATCH 3/3] fortify: move test_fortify.sh to lib/test_fortify/ Masahiro Yamada
2024-07-15 16:07 ` Kees Cook [this message]
2024-07-15 16:38   ` [PATCH 0/3] fortify: fix various issues in test_fortify Makefile Masahiro Yamada

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=202407150905.56BBE11@keescook \
    --to=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.