All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Wen Gu <guwen@linux.alibaba.com>,
	Philo Lu <lulie@linux.alibaba.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Dong Yibo <dong100@mucse.com>,
	Mingyu Wang <25181214217@stu.xidian.edu.cn>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Dust Li <dust.li@linux.alibaba.com>
Subject: Re: [PATCH net-next v41 0/7] eea: Add basic driver framework for Alibaba Elastic Ethernet Adaptor
Date: Thu, 30 Apr 2026 19:13:56 -0700	[thread overview]
Message-ID: <20260430191356.7a7183ac@kernel.org> (raw)
In-Reply-To: <20260429023726.100908-1-xuanzhuo@linux.alibaba.com>

On Wed, 29 Apr 2026 10:37:19 +0800 Xuan Zhuo wrote:
> Add a driver framework for EEA that will be available in the future.
> 
> This driver is currently quite minimal, implementing only fundamental
> core functionalities. Key features include: I/O queue management via
> adminq, basic PCI-layer operations, and essential RX/TX data
> communication capabilities. It also supports the creation,
> initialization, and management of network devices (netdev). Furthermore,
> the ring structures for both I/O queues and adminq have been abstracted
> into a simple, unified, and reusable library implementation,
> facilitating future extension and maintenance.
> 
> v41:
>     1. make https://sashiko.dev/ happy

Does not look happy, some of the reports / asks look valid. 
FWIW we have another sashiko instance now:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260429023726.100908-5-xuanzhuo@linux.alibaba.com
You should definitely follow the advice to rename the config,
and also failing probe because the FW doesn't like the kernel
version is not acceptable upstream. You can print a warning
but failure is not acceptable.
-- 
pw-bot: cr

      parent reply	other threads:[~2026-05-01  2:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  2:37 [PATCH net-next v41 0/7] eea: Add basic driver framework for Alibaba Elastic Ethernet Adaptor Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 1/7] eea: introduce PCI framework Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 2/7] eea: introduce ring and descriptor structures Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 3/7] eea: probe the netdevice and create adminq Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 4/7] eea: create/destroy rx,tx queues for netdevice open and stop Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 5/7] eea: implement packet receive logic Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 6/7] eea: implement packet transmit logic Xuan Zhuo
2026-04-29  2:37 ` [PATCH net-next v41 7/7] eea: introduce ethtool support Xuan Zhuo
2026-05-01  2:13 ` Jakub Kicinski [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=20260430191356.7a7183ac@kernel.org \
    --to=kuba@kernel.org \
    --cc=25181214217@stu.xidian.edu.cn \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dong100@mucse.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=hkallweit1@gmail.com \
    --cc=lulie@linux.alibaba.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.