From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Ahmad Fatoum <a.fatoum@barebox.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/5] security: add new top-level menu
Date: Thu, 7 Aug 2025 10:11:20 +0200 [thread overview]
Message-ID: <81c2da1b-f282-42c0-b2a1-c9f7982c66f2@pengutronix.de> (raw)
In-Reply-To: <aJRW-miZJt_QGl8A@pengutronix.de>
Hi,
On 8/7/25 09:34, Sascha Hauer wrote:
> Hi Ahmad,
>
> On Wed, Aug 06, 2025 at 04:00:01PM +0200, Ahmad Fatoum wrote:
>> +config SECURITY_POLICY
>> + bool
>> + prompt "Security policy support"
>> +
>
> ...
>
>> diff --git a/security/Makefile b/security/Makefile
>> new file mode 100644
>> index 000000000000..e0b17f12064c
>> --- /dev/null
>> +++ b/security/Makefile
>> @@ -0,0 +1,29 @@
>> +# SPDX-License-Identifier: GPL-2.0-only
>> +
>> +obj-$(CONFIG_SECURITY_POLICY) += sconfig.o sconfig_names.o
>
> We are not there yet ;)
Oh, sorry about that.
Is a fix up ok?
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-08-07 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 14:00 Ahmad Fatoum
2025-08-06 14:00 ` [PATCH 2/5] security: mark weaker passwords hashing algorithms insecure Ahmad Fatoum
2025-08-06 14:00 ` [PATCH 3/5] commands: introduce new security command group Ahmad Fatoum
2025-08-06 14:00 ` [PATCH 4/5] security: password: make PBKDF2 the default instead of MD5 Ahmad Fatoum
2025-08-06 14:00 ` [PATCH 5/5] commands: move login/passwd into security section Ahmad Fatoum
2025-08-07 6:26 ` [PATCH] fixup! security: add new top-level menu Ahmad Fatoum
2025-08-07 7:34 ` [PATCH 1/5] " Sascha Hauer
2025-08-07 8:11 ` Ahmad Fatoum [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=81c2da1b-f282-42c0-b2a1-c9f7982c66f2@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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