From: Jakub Kicinski <kuba@kernel.org>
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Simon Horman <horms@kernel.org>, Brett Creeley <bcreeley@amd.com>,
Ratheesh Kannoth <rkannoth@marvell.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel
Date: Tue, 16 Apr 2024 19:29:52 -0700 [thread overview]
Message-ID: <20240416192952.1e740891@kernel.org> (raw)
In-Reply-To: <1abdb66a-a080-424e-847d-1d2f5837bbc4@linux.alibaba.com>
On Wed, 17 Apr 2024 10:22:52 +0800 Heng Qi wrote:
> Have you encountered compilation problems in v8?
Yes, please try building allmodconfig:
make allmodconfig
make ..
there's many drivers using this API, you gotta build the full kernel..
next prev parent reply other threads:[~2024-04-17 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:29 [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 1/4] linux/dim: move useful macros to .h file Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 2/4] ethtool: provide customized dim profile management Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 3/4] virtio-net: refactor dim initialization/destruction Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 4/4] virtio-net: support dim profile fine-tuning Heng Qi
2024-04-17 0:38 ` [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel Jakub Kicinski
2024-04-17 2:22 ` Heng Qi
2024-04-17 2:29 ` Jakub Kicinski [this message]
2024-04-17 2:53 ` Jason Xing
2024-04-17 6:35 ` Heng Qi
2024-04-17 6:52 ` Jason Xing
2024-04-17 8:04 ` Heng Qi
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=20240416192952.1e740891@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=bcreeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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).