All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Vlad Pruteanu <vlad.pruteanu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, mihai-octavian.urzica@nxp.com,
	iulia.tanasescu@nxp.com, andrei.istodorescu@nxp.com,
	luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ v2 0/2] bap: Allocate memory for broadcast code
Date: Wed, 19 Jun 2024 14:10:29 +0000	[thread overview]
Message-ID: <171880622906.19669.10788137030713318361.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240619095119.167652-1-vlad.pruteanu@nxp.com>

Hello:

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

On Wed, 19 Jun 2024 12:51:17 +0300 you wrote:
> Currently the broadcast code is set without memory being allocated
> for it resulting in segmentation fault. This implements an util_iov_new
> function that allocates the memory before setting the user_data. The issue is
> fixed by using this function instead of util_iov_append.
> 
> Vlad Pruteanu (2):
>   shared/util: Add util_iov_new function
>   bap: Use util_iov_new when setting bcode
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/2] shared/util: Add util_iov_new function
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=503ecbc655c5
  - [BlueZ,v2,2/2] bap: Use util_iov_new when setting bcode
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5ec05848a9d4

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



      parent reply	other threads:[~2024-06-19 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  9:51 [PATCH BlueZ v2 0/2] bap: Allocate memory for broadcast code Vlad Pruteanu
2024-06-19  9:51 ` [PATCH BlueZ v2 1/2] shared/util: Add util_iov_new function Vlad Pruteanu
2024-06-19 12:07   ` bap: Allocate memory for broadcast code bluez.test.bot
2024-06-19  9:51 ` [PATCH BlueZ v2 2/2] bap: Use util_iov_new when setting bcode Vlad Pruteanu
2024-06-19 14:10 ` 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=171880622906.19669.10788137030713318361.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=andrei.istodorescu@nxp.com \
    --cc=iulia.tanasescu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mihai-octavian.urzica@nxp.com \
    --cc=vlad.pruteanu@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.