public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Christian Eggers <ceggers@arri.de>
Cc: brian.gix@gmail.com, inga.stotland@gmail.com,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH Bluez v2 0/9] mesh: cleanups and a bugfix for relay packets
Date: Tue, 15 Jul 2025 14:30:10 +0000	[thread overview]
Message-ID: <175258981065.461397.15820775551050380963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711220035.10065-1-ceggers@arri.de>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 11 Jul 2025 23:57:12 +0200 you wrote:
> The first 3 patches replace further magic numbers by preprocessor
> defines (no functional changes). Patch 4 tries to improve readabilty,
> while 5 and 6 are only cleanups (these patches have already been
> submitted in my previous series, but were not merged without any
> notice).
> 
> Patch 7 and 8 are further simplifications/cleanups, while the last patch
> fixes a serious bug which causes corruption in all relayed packets. Maybe
> this NEVER worked correctly, although this is a major feature of
> Bluetooth Mesh. At leat this one should get reviewied by a Mesh expert.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/9] mesh: net-keys: more uses of BEACON_LEN_SNB and BEACON_LEN_MPB
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=009cfb5188f8
  - [BlueZ,v2,2/9] mesh: introduce MESH_AD_MAX_LEN and MESH_NET_MAX_PDU_LEN
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=646cbe922792
  - [BlueZ,v2,3/9] mesh: replace MESH internal defines by shared ones
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cd651d8e21d7
  - [BlueZ,v2,4/9] mesh: net: constify tx path
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b692d72b15b3
  - [BlueZ,v2,5/9] mesh: net: remove unused stuff
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0e586df2d0ae
  - [BlueZ,v2,6/9] mesh: net: update comment
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cb4b20c71fd3
  - [BlueZ,v2,7/9] mesh: crypto: mesh_crypto_aes_ccm_encrypt(): remove unused parameter
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9a32ff5aa7ed
  - [BlueZ,v2,8/9] mesh: crypto: simplify mesh_crypto_packet_parse()
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=159101c7bc38
  - [BlueZ,v2,9/9] mesh: fix corrupted relay packets
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2b0a6fa08407

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



      parent reply	other threads:[~2025-07-15 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 21:57 [PATCH Bluez v2 0/9] mesh: cleanups and a bugfix for relay packets Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 1/9] mesh: net-keys: more uses of BEACON_LEN_SNB and BEACON_LEN_MPB Christian Eggers
2025-07-11 23:26   ` mesh: cleanups and a bugfix for relay packets bluez.test.bot
2025-07-11 21:57 ` [PATCH BlueZ v2 2/9] mesh: introduce MESH_AD_MAX_LEN and MESH_NET_MAX_PDU_LEN Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 3/9] mesh: replace MESH internal defines by shared ones Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 4/9] mesh: net: constify tx path Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 5/9] mesh: net: remove unused stuff Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 6/9] mesh: net: update comment Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 7/9] mesh: crypto: mesh_crypto_aes_ccm_encrypt(): remove unused parameter Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 8/9] mesh: crypto: simplify mesh_crypto_packet_parse() Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 9/9] mesh: fix corrupted relay packets Christian Eggers
2025-07-15 14:30 ` patchwork-bot+bluetooth [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=175258981065.461397.15820775551050380963.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=brian.gix@gmail.com \
    --cc=ceggers@arri.de \
    --cc=inga.stotland@gmail.com \
    --cc=linux-bluetooth@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