From: patchwork-bot+netdevbpf@kernel•org
To: Li Li <dualli@chromium•org>
Cc: dualli@google•com, corbet@lwn•net, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
donald.hunter@gmail•com, gregkh@linuxfoundation•org,
arve@android•com, tkjos@android•com, maco@android•com,
joel@joelfernandes•org, brauner@kernel•org, cmllamas@google•com,
surenb@google•com, arnd@arndb•de, masahiroy@kernel•org,
bagasdotme@gmail•com, horms@kernel•org,
linux-kernel@vger•kernel.org, linux-doc@vger•kernel.org,
netdev@vger•kernel.org, hridya@google•com, smoreland@google•com,
kernel-team@android•com
Subject: Re: [PATCH net-next v8 0/2] binder: report txn errors via generic netlink
Date: Tue, 19 Nov 2024 02:50:44 +0000 [thread overview]
Message-ID: <173198464425.82509.5510498635851366417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241113193239.2113577-1-dualli@chromium.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 13 Nov 2024 11:32:37 -0800 you wrote:
> From: Li Li <dualli@google•com>
>
> It's a known issue that neither the frozen processes nor the system
> administration process of the OS can correctly deal with failed binder
> transactions. The reason is that there's no reliable way for the user
> space administration process to fetch the binder errors from the kernel
> binder driver.
>
> [...]
Here is the summary with links:
- [net-next,v8,1/2] tools: ynl-gen: allow uapi headers in sub-dirs
https://git.kernel.org/netdev/net-next/c/6204656478be
- [net-next,v8,2/2] binder: report txn errors via generic netlink
(no matching commit)
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:[~2024-11-19 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 19:32 [PATCH net-next v8 0/2] binder: report txn errors via generic netlink Li Li
2024-11-13 19:32 ` [PATCH net-next v8 1/2] tools: ynl-gen: allow uapi headers in sub-dirs Li Li
2024-11-13 19:32 ` [PATCH net-next v8 2/2] binder: report txn errors via generic netlink Li Li
2024-11-17 7:23 ` kernel test robot
2024-12-05 2:35 ` Jakub Kicinski
2024-12-05 12:01 ` Li Li
2024-12-06 0:33 ` Jakub Kicinski
2024-11-19 2:37 ` [PATCH net-next v8 0/2] " Jakub Kicinski
2024-11-19 2:50 ` patchwork-bot+netdevbpf [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=173198464425.82509.5510498635851366417.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=arve@android$(echo .)com \
--cc=bagasdotme@gmail$(echo .)com \
--cc=brauner@kernel$(echo .)org \
--cc=cmllamas@google$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=dualli@chromium$(echo .)org \
--cc=dualli@google$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=hridya@google$(echo .)com \
--cc=joel@joelfernandes$(echo .)org \
--cc=kernel-team@android$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maco@android$(echo .)com \
--cc=masahiroy@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=smoreland@google$(echo .)com \
--cc=surenb@google$(echo .)com \
--cc=tkjos@android$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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