Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Schmidt <mschmidt@redhat.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: [Intel-wired-lan] [PATCH iwl-next 0/4] iavf: cleanups, dead code removal
Date: Mon, 16 Oct 2023 18:48:45 +0200	[thread overview]
Message-ID: <20231016164849.45691-1-mschmidt@redhat.com> (raw)

The first 3 patches are quite simple cleanups.
Patch 4 removes the whole unused iavf client interface and the
supporting code.

Michal Schmidt (4):
  iavf: rely on netdev's own registered state
  iavf: use unregister_netdev
  iavf: add a common function for undoing the interrupt scheme
  iavf: delete the iavf client interface

 drivers/net/ethernet/intel/iavf/Makefile      |   2 +-
 drivers/net/ethernet/intel/iavf/iavf.h        |  28 -
 drivers/net/ethernet/intel/iavf/iavf_client.c | 578 ------------------
 drivers/net/ethernet/intel/iavf/iavf_client.h | 169 -----
 drivers/net/ethernet/intel/iavf/iavf_main.c   | 121 +---
 .../net/ethernet/intel/iavf/iavf_virtchnl.c   |  14 -
 6 files changed, 20 insertions(+), 892 deletions(-)
 delete mode 100644 drivers/net/ethernet/intel/iavf/iavf_client.c
 delete mode 100644 drivers/net/ethernet/intel/iavf/iavf_client.h

-- 
2.41.0

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

             reply	other threads:[~2023-10-16 16:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 16:48 Michal Schmidt [this message]
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 1/4] iavf: rely on netdev's own registered state Michal Schmidt
2023-10-17  8:01   ` Drewek, Wojciech
2023-10-17 17:30   ` Jacob Keller
2023-10-24  9:09     ` Romanowski, Rafal
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 2/4] iavf: use unregister_netdev Michal Schmidt
2023-10-17  8:06   ` Drewek, Wojciech
2023-10-24  9:11     ` Romanowski, Rafal
2023-10-17 17:33   ` Jacob Keller
2023-10-17 18:43     ` Jacob Keller
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 3/4] iavf: add a common function for undoing the interrupt scheme Michal Schmidt
2023-10-17  8:58   ` Drewek, Wojciech
2023-10-17 17:35   ` Jacob Keller
2023-10-24  9:12     ` Romanowski, Rafal
2023-10-16 16:48 ` [Intel-wired-lan] [PATCH iwl-next 4/4] iavf: delete the iavf client interface Michal Schmidt
2023-10-17 17:46   ` Jacob Keller
2023-10-24  9:12     ` Romanowski, Rafal

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=20231016164849.45691-1-mschmidt@redhat.com \
    --to=mschmidt@redhat.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    /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