From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kvalo@kernel.org,
pkshih@realtek.com, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] codel: remove unnecessary sock.h include
Date: Thu, 23 Dec 2021 00:50:09 +0000 [thread overview]
Message-ID: <164022060966.21673.3814438675172430394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211221193941.3805147-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 21 Dec 2021 11:39:40 -0800 you wrote:
> Since sock.h is modified relatively often (60 times in the last
> 12 months) it seems worthwhile to decrease the incremental build
> work.
>
> CoDel's header includes net/inet_ecn.h which in turn includes net/sock.h.
> codel.h is itself included by mac80211 which is included by much of
> the WiFi stack and drivers. Removing the net/inet_ecn.h include from
> CoDel breaks the dependecy between WiFi and sock.h.
>
> [...]
Here is the summary with links:
- [net-next,1/2] codel: remove unnecessary sock.h include
https://git.kernel.org/netdev/net-next/c/15fcb1031178
- [net-next,2/2] codel: remove unnecessary pkt_sched.h include
https://git.kernel.org/netdev/net-next/c/e6e590445581
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-12-23 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 19:39 [PATCH net-next 1/2] codel: remove unnecessary sock.h include Jakub Kicinski
2021-12-21 19:39 ` [PATCH net-next 2/2] codel: remove unnecessary pkt_sched.h include Jakub Kicinski
2021-12-22 5:58 ` Kalle Valo
2021-12-22 5:56 ` [PATCH net-next 1/2] codel: remove unnecessary sock.h include Kalle Valo
2021-12-23 0: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=164022060966.21673.3814438675172430394.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.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).