From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] acl updates for v6.2
Date: Mon, 12 Dec 2022 18:56:59 -0800 [thread overview]
Message-ID: <CAHk-=witvjWrYOqbgURdeH7cv7bkVT5O2wd_HcoY6L-3_3yK8A@mail.gmail.com> (raw)
In-Reply-To: <20221212111919.98855-1-brauner@kernel.org>
On Mon, Dec 12, 2022 at 3:19 AM Christian Brauner <brauner@kernel.org> wrote:
>
> For a long and detailed
> explanation for just some of the issues [1] provides a good summary.
There is no link [1].
> A few implementation details:
>
> * The series makes sure to retain exactly the same security and integrity module
> permission checks. See [2] for annotated callchains.
There is no link [2].
This was an extensive changelog for my merge commit, so it's all fine
and I've pulled it, but it does look like some pieces were either
missing, or there was a bit of a cut-and-paste from previous
explanations without the links..
Linus
next prev parent reply other threads:[~2022-12-13 2:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:19 [GIT PULL] acl updates for v6.2 Christian Brauner
2022-12-13 2:56 ` Linus Torvalds [this message]
2022-12-13 9:09 ` Christian Brauner
2022-12-13 3:49 ` pr-tracker-bot
2022-12-27 15:27 ` J. R. Okajima
2022-12-27 18:31 ` Christian Brauner
2022-12-27 23:54 ` hooanon05g
2023-01-04 0:57 ` hooanon05g
2023-01-04 10:04 ` Linux kernel regression tracking (#info)
2023-01-04 10:14 ` Christian Brauner
2023-01-04 10:26 ` Thorsten Leemhuis
2023-01-04 10:37 ` Christian Brauner
2022-12-28 8:40 ` [GIT PULL] acl updates for v6.2 #forregzbot Thorsten Leemhuis
2023-01-01 20:07 ` J. R. Okajima
2023-01-02 7:25 ` Thorsten Leemhuis
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='CAHk-=witvjWrYOqbgURdeH7cv7bkVT5O2wd_HcoY6L-3_3yK8A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).