From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2022-07-22
Date: Mon, 01 Aug 2022 21:15:46 +0000 [thread overview]
Message-ID: <165938854663.17345.13441892409944440799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220723002232.964796-1-luiz.dentz@gmail.com>
Hello:
This pull request was applied to bluetooth/bluetooth-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 22 Jul 2022 17:22:32 -0700 you wrote:
> The following changes since commit 6e0e846ee2ab01bc44254e6a0a6a6a0db1cba16d:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2022-07-21 13:03:39 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git tags/for-net-next-2022-07-22
>
> [...]
Here is the summary with links:
- pull request: bluetooth-next 2022-07-22
https://git.kernel.org/bluetooth/bluetooth-next/c/4a934eca7b39
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-01 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 0:22 pull request: bluetooth-next 2022-07-22 Luiz Augusto von Dentz
2022-07-23 2:10 ` patchwork-bot+netdevbpf
2022-08-01 21:15 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 20:54 Luiz Augusto von Dentz
2022-07-22 23:55 ` Jakub Kicinski
2022-07-23 0:09 ` Luiz Augusto von Dentz
2022-07-23 0:19 ` Jakub Kicinski
2022-07-23 0:25 ` Luiz Augusto von Dentz
2022-07-23 0:50 ` Jakub Kicinski
2022-07-26 22:05 ` Luiz Augusto von Dentz
2022-07-26 22:31 ` Jakub Kicinski
2022-07-27 1:06 ` Luiz Augusto von Dentz
2022-07-27 2:47 ` Jakub Kicinski
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=165938854663.17345.13441892409944440799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).