linux-kernel - Re: [PATCH] block: Name the RQF flags enum

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174190325773.1674705.18381879459653855191.git-patchwork-notify@kernel.org>
Date: Thu, 13 Mar 2025 22:00:57 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Breno Leitao <leitao@...ian.org>
Cc: axboe@...nel.dk, linux-block@...r.kernel.org,
 linux-kernel@...r.kernel.org, bpf@...r.kernel.org, kernel-team@...a.com,
 yonghong.song@...ux.dev
Subject: Re: [PATCH] block: Name the RQF flags enum

Hello:

This patch was applied to netdev/net.git (main)
by Jens Axboe <axboe@...nel.dk>:

On Thu, 06 Mar 2025 08:27:51 -0800 you wrote:
> Commit 5f89154e8e9e3445f9b59 ("block: Use enum to define RQF_x bit
> indexes") converted the RQF flags to an anonymous enum, which was
> a beneficial change. This patch goes one step further by naming the enum
> as "rqf_flags".
> 
> This naming enables exporting these flags to BPF clients, eliminating
> the need to duplicate these flags in BPF code. Instead, BPF clients can
> now access the same kernel-side values through CO:RE (Compile Once, Run
> Everywhere), as shown in this example:
> 
> [...]

Here is the summary with links:
  - block: Name the RQF flags enum
    https://git.kernel.org/netdev/net/c/e7112524e5e8

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