From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, matt@codeconstruct.com.au,
davem@davemloft.net, kuba@kernel.org, esyr@redhat.com,
geert@linux-m68k.org
Subject: Re: [PATCH net 1/2] mctp: unify sockaddr_mctp types
Date: Mon, 18 Oct 2021 13:00:07 +0000 [thread overview]
Message-ID: <163456200736.664.14926664578207340379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211018032935.2092613-1-jk@codeconstruct.com.au>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 18 Oct 2021 11:29:34 +0800 you wrote:
> Use the more precise __kernel_sa_family_t for smctp_family, to match
> struct sockaddr.
>
> Also, use an unsigned int for the network member; negative networks
> don't make much sense. We're already using unsigned for mctp_dev and
> mctp_skb_cb, but need to change mctp_sock to suit.
>
> [...]
Here is the summary with links:
- [net,1/2] mctp: unify sockaddr_mctp types
https://git.kernel.org/netdev/net/c/b416beb25d93
- [net,2/2] mctp: Be explicit about struct sockaddr_mctp padding
https://git.kernel.org/netdev/net/c/5a20dd46b8b8
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-18 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 3:29 [PATCH net 1/2] mctp: unify sockaddr_mctp types Jeremy Kerr
2021-10-18 3:29 ` [PATCH net 2/2] mctp: Be explicit about struct sockaddr_mctp padding Jeremy Kerr
2021-10-18 12:51 ` Eugene Syromiatnikov
2021-10-18 12:00 ` [PATCH net 1/2] mctp: unify sockaddr_mctp types Eugene Syromiatnikov
2021-10-18 13:00 ` 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=163456200736.664.14926664578207340379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=esyr@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--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).