From: Lincoln Wallace <locnnil0@gmail.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
paul@paul-moore.com, corbet@lwn.net
Cc: skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp, rdunlap@infradead.org
Subject: Re: [PATCH 0/2] doc: LSM: update usage document for current LSM stacking
Date: Thu, 23 Jul 2026 21:24:59 -0300 [thread overview]
Message-ID: <amKuTh0WV1vhvA93@gmail.com> (raw)
In-Reply-To: <d14f03a6-2c48-4f96-8682-29453945b29d@schaufler-ca.com>
On Thu, Jul 23, 2026 at 10:47:12AM -0700, Casey Schaufler wrote:
> I've been stewing on this since it came up. We should probably
> remove the somewhat complicated logic from the Kconfig files if
> it's not adding value.
That seems worth doing, but it looks like a separate change to me.
The document currently describes behaviour the code does not have,
and that's worth correcting either way. If the Kconfig is simplified
later, updating these paragraphs again should be a small part of that
series.
Happy to help with the Kconfig cleanup if that would be useful.
Do you see anything in the two patches that needs adjusting as they
stand?
prev parent reply other threads:[~2026-07-24 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 1:38 [PATCH 0/2] doc: LSM: update usage document for current LSM stacking Lincoln Wallace
2026-07-14 1:38 ` [PATCH 1/2] doc: LSM: describe CONFIG_LSM and lsm= as the selection mechanism Lincoln Wallace
2026-07-14 1:38 ` [PATCH 2/2] doc: LSM: fix module ordering description for /sys/kernel/security/lsm Lincoln Wallace
2026-07-23 17:47 ` [PATCH 0/2] doc: LSM: update usage document for current LSM stacking Casey Schaufler
2026-07-24 0:24 ` Lincoln Wallace [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=amKuTh0WV1vhvA93@gmail.com \
--to=locnnil0@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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