From: patchwork-bot+netdevbpf@kernel.org
To: Dave Thaler <dthaler1968@googlemail.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org, dthaler@microsoft.com
Subject: Re: [PATCH bpf-next] bpf, docs: Define signed modulo as using truncated division
Date: Wed, 18 Oct 2023 23:40:23 +0000 [thread overview]
Message-ID: <169767242338.29372.2996084798084133663.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231017203020.1500-1-dthaler1968@googlemail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 17 Oct 2023 20:30:20 +0000 you wrote:
> From: Dave Thaler <dthaler@microsoft.com>
>
> There's different mathematical definitions (truncated, floored,
> rounded, etc.) and different languages have chosen different
> definitions [0][1]. E.g., languages/libraries that follow Knuth
> use a different mathematical definition than C uses. This
> patch specifies which definition BPF uses, as verified by
> Eduard [2] and others.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, docs: Define signed modulo as using truncated division
https://git.kernel.org/bpf/bpf-next/c/0e133a133703
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-18 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:30 [PATCH bpf-next] bpf, docs: Define signed modulo as using truncated division Dave Thaler
2023-10-17 20:30 ` [Bpf] " Dave Thaler
2023-10-18 22:28 ` David Vernet
2023-10-18 22:28 ` [Bpf] " David Vernet
2023-10-18 22:34 ` Eduard Zingerman
2023-10-18 23:40 ` Daniel Borkmann
2023-10-18 23:40 ` [Bpf] " Daniel Borkmann
2023-10-19 0:00 ` Eduard Zingerman
2023-10-19 0:00 ` [Bpf] " Eduard Zingerman
2023-10-18 23:40 ` 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=169767242338.29372.2996084798084133663.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@googlemail.com \
--cc=dthaler@microsoft.com \
/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