public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, brauner@kernel.org, jiejiang@chromium.org,
	andrii@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Re-support uid and gid when mounting bpffs
Date: Thu, 21 Dec 2023 13:30:24 +0000	[thread overview]
Message-ID: <170316542444.15316.13410322565647392236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231220133805.20953-1-daniel@iogearbox.net>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 20 Dec 2023 14:38:05 +0100 you wrote:
> For a clean, conflict-free revert of the token-related patches in commit
> d17aff807f84 ("Revert BPF token-related functionality"), the bpf fs commit
> 750e785796bb ("bpf: Support uid and gid when mounting bpffs") was undone
> temporarily as well.
> 
> This patch manually re-adds the functionality from the original one back
> in 750e785796bb, no other functional changes intended.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: Re-support uid and gid when mounting bpffs
    https://git.kernel.org/bpf/bpf-next/c/b08c8fc0411d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-12-21 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 13:38 [PATCH bpf-next] bpf: Re-support uid and gid when mounting bpffs Daniel Borkmann
2023-12-21 13:10 ` Christian Brauner
2023-12-21 13:30 ` patchwork-bot+netdevbpf [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=170316542444.15316.13410322565647392236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jiejiang@chromium.org \
    --cc=linux-fsdevel@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