From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf-next 2024-04-29
Date: Mon, 29 Apr 2024 13:22:07 -0700 [thread overview]
Message-ID: <20240429132207.58ecf430@kernel.org> (raw)
In-Reply-To: <20240429131657.19423-1-daniel@iogearbox.net>
On Mon, 29 Apr 2024 15:16:57 +0200 Daniel Borkmann wrote:
> tools: Add ethtool.h header to tooling infra
Could you follow up to remove this header?
Having to keep multiple headers in sync is annoying, and using
'make headers' or including in-tree headers directly is not rocket
science.
next prev parent reply other threads:[~2024-04-29 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 13:16 pull-request: bpf-next 2024-04-29 Daniel Borkmann
2024-04-29 20:22 ` Jakub Kicinski [this message]
2024-04-29 21:14 ` Daniel Borkmann
2024-04-30 8:03 ` Vyavahare, Tushar
2024-04-30 8:16 ` Magnus Karlsson
2024-04-30 13:45 ` Jakub Kicinski
2024-04-29 20:30 ` patchwork-bot+netdevbpf
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=20240429132207.58ecf430@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).