From: patchwork-bot+bluetooth@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, alexander@mihalicyn.com, brauner@kernel.org,
luiz.von.dentz@intel.com, kuni1840@gmail.com,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1 net-next 0/2] af_unix: Followup fixes for SO_PASSPIDFD.
Date: Tue, 27 Jun 2023 19:01:53 +0000 [thread overview]
Message-ID: <168789251341.11348.5241440174968893552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230627174314.67688-1-kuniyu@amazon.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jun 2023 10:43:12 -0700 you wrote:
> This series fixes 2 issues introduced by commit 5e2ff6704a27 ("scm: add
> SO_PASSPIDFD and SCM_PIDFD").
>
> The 1st patch fixes a warning in scm_pidfd_recv() reported by syzkaller.
> The 2nd patch fixes a regression that bluetooth can't be built as module.
>
>
> [...]
Here is the summary with links:
- [v1,net-next,1/2] af_unix: Skip SCM_PIDFD if scm->pid is NULL.
https://git.kernel.org/bluetooth/bluetooth-next/c/603fc57ab70c
- [v1,net-next,2/2] net: scm: introduce and use scm_recv_unix helper
https://git.kernel.org/bluetooth/bluetooth-next/c/a9c49cc2f5b5
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-06-27 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 17:43 [PATCH v1 net-next 0/2] af_unix: Followup fixes for SO_PASSPIDFD Kuniyuki Iwashima
2023-06-27 17:43 ` [PATCH v1 net-next 1/2] af_unix: Skip SCM_PIDFD if scm->pid is NULL Kuniyuki Iwashima
2023-06-27 17:43 ` [PATCH v1 net-next 2/2] net: scm: introduce and use scm_recv_unix helper Kuniyuki Iwashima
2023-06-27 18:10 ` [PATCH v1 net-next 0/2] af_unix: Followup fixes for SO_PASSPIDFD patchwork-bot+netdevbpf
2023-06-27 19:01 ` 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=168789251341.11348.5241440174968893552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).