All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: aleksander.lobakin@intel.com,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	michal.swiatkowski@linux.intel.com, michal.kubiak@intel.com,
	maciej.fijalkowski@intel.com, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [Intel-wired-lan] [PATCH net-next 1/8] i40e: extract GRXRINGS from .get_rxnfc
Date: Mon, 24 Nov 2025 19:48:23 -0800	[thread overview]
Message-ID: <20251124194823.79d393ab@kernel.org> (raw)
In-Reply-To: <20251124-gxring_intel-v1-1-89be18d2a744@debian.org>

On Mon, 24 Nov 2025 10:19:05 -0800 Breno Leitao wrote:
> + * Returns the number of RX rings.

I suspect you used this format because the rest of the driver does,
but let's avoid adding new kdoc warnings. I think Andy is trying
to clean up the "Returns" vs "Return:" in Intel drivers..

 drivers/net/ethernet/intel/i40e/i40e_ethtool.c:3530 No description found for return value of 'i40e_get_rx_ring_count'

(similar warnings to first 4 patches of the series)
-- 
pw-bot: cr

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: aleksander.lobakin@intel.com,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	michal.swiatkowski@linux.intel.com, michal.kubiak@intel.com,
	maciej.fijalkowski@intel.com, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH net-next 1/8] i40e: extract GRXRINGS from .get_rxnfc
Date: Mon, 24 Nov 2025 19:48:23 -0800	[thread overview]
Message-ID: <20251124194823.79d393ab@kernel.org> (raw)
In-Reply-To: <20251124-gxring_intel-v1-1-89be18d2a744@debian.org>

On Mon, 24 Nov 2025 10:19:05 -0800 Breno Leitao wrote:
> + * Returns the number of RX rings.

I suspect you used this format because the rest of the driver does,
but let's avoid adding new kdoc warnings. I think Andy is trying
to clean up the "Returns" vs "Return:" in Intel drivers..

 drivers/net/ethernet/intel/i40e/i40e_ethtool.c:3530 No description found for return value of 'i40e_get_rx_ring_count'

(similar warnings to first 4 patches of the series)
-- 
pw-bot: cr

  reply	other threads:[~2025-11-25  3:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 18:19 [Intel-wired-lan] [PATCH net-next 0/8] net: intel: migrate to .get_rx_ring_count() ethtool callback Breno Leitao
2025-11-24 18:19 ` Breno Leitao
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 1/8] i40e: extract GRXRINGS from .get_rxnfc Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  3:48   ` Jakub Kicinski [this message]
2025-11-25  3:48     ` Jakub Kicinski
2025-11-25  9:21     ` [Intel-wired-lan] " Breno Leitao
2025-11-25  9:21       ` Breno Leitao
2025-11-25  6:50   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:50     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 2/8] iavf: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:50   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:50     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 3/8] ice: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:49     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 4/8] idpf: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:48   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:48     ` Loktionov, Aleksandr
2025-11-25  9:22     ` Breno Leitao
2025-11-25  6:49   ` Loktionov, Aleksandr
2025-11-25  6:49     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 5/8] igb: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:49     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 6/8] igc: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:49     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 7/8] ixgbevf: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:48   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:48     ` Loktionov, Aleksandr
2025-11-24 18:19 ` [Intel-wired-lan] [PATCH net-next 8/8] fm10k: " Breno Leitao
2025-11-24 18:19   ` Breno Leitao
2025-11-25  6:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-25  6:49     ` Loktionov, Aleksandr

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=20251124194823.79d393ab@kernel.org \
    --to=kuba@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kernel-team@meta.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=michal.kubiak@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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.