All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Bluetooth: Add proper definitions for scan interval and window
Date: Mon, 01 Apr 2024 14:10:29 +0000	[thread overview]
Message-ID: <171198062957.26711.17394152526175013459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240328201554.1791904-1-luiz.dentz@gmail.com>

Hello:

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

On Thu, 28 Mar 2024 16:15:53 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This adds proper definitions for scan interval and window and then make
> use of them instead their values.
> 
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> [...]

Here is the summary with links:
  - [v1,1/2] Bluetooth: Add proper definitions for scan interval and window
    https://git.kernel.org/bluetooth/bluetooth-next/c/3fa47b12cd09
  - [v1,2/2] Bluetooth: hci_sync: Fix using the same interval and window for Coded PHY
    https://git.kernel.org/bluetooth/bluetooth-next/c/0d5395c0c5b5

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-04-01 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 20:15 [PATCH v1 1/2] Bluetooth: Add proper definitions for scan interval and window Luiz Augusto von Dentz
2024-03-28 20:15 ` [PATCH v1 2/2] Bluetooth: hci_sync: Fix using the same interval and window for Coded PHY Luiz Augusto von Dentz
2024-03-28 20:56 ` [v1,1/2] Bluetooth: Add proper definitions for scan interval and window bluez.test.bot
2024-04-01 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=171198062957.26711.17394152526175013459.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.