From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jiang.wang@bytedance.com, andrii@kernel.org,
cong.wang@bytedance.com, jakub@cloudflare.com,
john.fastabend@gmail.com, digetx@gmail.com
Subject: Re: [PATCH] af_unix: Rename UNIX-DGRAM to UNIX to maintain backwards compatability
Date: Tue, 12 Oct 2021 10:20:06 +0000 [thread overview]
Message-ID: <163403400678.16702.616769036972068377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211008215946.3961353-1-swboyd@chromium.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Oct 2021 14:59:45 -0700 you wrote:
> Then name of this protocol changed in commit 94531cfcbe79 ("af_unix: Add
> unix_stream_proto for sockmap") because that commit added stream support
> to the af_unix protocol. Renaming the existing protocol makes a ChromeOS
> protocol test[1] fail now that the name has changed in
> /proc/net/protocols from "UNIX" to "UNIX-DGRAM".
>
> Let's put the name back to how it was while keeping the stream protocol
> as "UNIX-STREAM" so that the procfs interface doesn't change. This fixes
> the test and maintains backwards compatibility in proc.
>
> [...]
Here is the summary with links:
- af_unix: Rename UNIX-DGRAM to UNIX to maintain backwards compatability
https://git.kernel.org/netdev/net/c/0edf0824e0dc
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:[~2021-10-12 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 21:59 [PATCH] af_unix: Rename UNIX-DGRAM to UNIX to maintain backwards compatability Stephen Boyd
2021-10-12 10:20 ` 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=163403400678.16702.616769036972068377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=digetx@gmail.com \
--cc=jakub@cloudflare.com \
--cc=jiang.wang@bytedance.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swboyd@chromium.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