From: patchwork-bot+netdevbpf@kernel.org
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kuba@kernel.org, jmaloy@redhat.com, ying.xue@windriver.com,
arnd@arndb.de, masahiroy@kernel.org, dhowells@redhat.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net, uapi: remove inclusion of arpa/inet.h
Date: Wed, 06 Apr 2022 13:10:14 +0000 [thread overview]
Message-ID: <164925061407.5679.9432370761204809582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220404175448.46200-1-ndesaulniers@google.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 4 Apr 2022 10:54:47 -0700 you wrote:
> In include/uapi/linux/tipc_config.h, there's a comment that it includes
> arpa/inet.h for ntohs; but ntohs is not defined in any UAPI header. For
> now, reuse the definitions from include/linux/byteorder/generic.h, since
> the various conversion functions do exist in UAPI headers:
> include/uapi/linux/byteorder/big_endian.h
> include/uapi/linux/byteorder/little_endian.h
>
> [...]
Here is the summary with links:
- [net-next,v3] net, uapi: remove inclusion of arpa/inet.h
https://git.kernel.org/netdev/net-next/c/1ee375d77bb9
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-04-06 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 21:29 [PATCH] net, uapi: remove inclusion of arpa/inet.h Nick Desaulniers
2022-03-29 21:50 ` Nick Desaulniers
2022-03-29 22:09 ` Nick Desaulniers
2022-03-29 22:26 ` Nick Desaulniers
2022-03-29 22:39 ` [PATCH v2] " Nick Desaulniers
2022-03-29 23:01 ` Jakub Kicinski
2022-03-29 23:12 ` Nick Desaulniers
2022-04-04 17:54 ` [PATCH net-next v3] " Nick Desaulniers
2022-04-06 13:10 ` patchwork-bot+netdevbpf [this message]
2022-03-30 6:08 ` [PATCH] " Arnd Bergmann
2022-03-30 6:11 ` Arnd Bergmann
2022-03-29 23:03 ` Nick Desaulniers
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=164925061407.5679.9432370761204809582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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