Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Dumazet <edumazet@google.com>,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH 33/35] drivers/net/ethernet/intel: Reorganize kerneldoc parameter names
Date: Mon, 30 Sep 2024 14:14:44 -0700	[thread overview]
Message-ID: <5cd9480f-1d26-a98a-5e56-1e827a64fddc@intel.com> (raw)
In-Reply-To: <20240930112121.95324-34-Julia.Lawall@inria.fr>



On 9/30/2024 4:21 AM, Julia Lawall wrote:
> Reorganize kerneldoc parameter names to match the parameter
> order in the function header.
> 
> Problems identified using Coccinelle.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>

> 
> ---
>   drivers/net/ethernet/intel/e1000/e1000_hw.c     |    2 +-
>   drivers/net/ethernet/intel/i40e/i40e_common.c   |    7 +++----
>   drivers/net/ethernet/intel/ice/ice_common.c     |    2 +-
>   drivers/net/ethernet/intel/ixgbe/ixgbe_common.c |    2 +-
>   4 files changed, 6 insertions(+), 7 deletions(-)

  reply	other threads:[~2024-09-30 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 11:20 [Intel-wired-lan] [PATCH 00/35] Reorganize kerneldoc parameter names Julia Lawall
2024-09-30 11:21 ` [Intel-wired-lan] [PATCH 33/35] drivers/net/ethernet/intel: " Julia Lawall
2024-09-30 21:14   ` Tony Nguyen [this message]
2024-10-06  1:55 ` [Intel-wired-lan] (subset) [PATCH 00/35] " Bjorn Andersson
2024-11-17 12:09 ` Michael Ellerman
2024-12-20 17:27 ` Srinivas Kandagatla

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=5cd9480f-1d26-a98a-5e56-1e827a64fddc@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox