Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Yue Haibing <yuehaibing@huawei.com>, <anthony.l.nguyen@intel.com>,
	<przemyslaw.kitszel@intel.com>, <davem@davemloft.net>,
	<kuba@kernel.org>, <pabeni@redhat.com>, <ahmed.zaki@intel.com>,
	<richardcochran@gmail.com>, <michal.swiatkowski@linux.intel.com>,
	<amritha.nambiar@intel.com>, <mateusz.polchlopek@intel.com>,
	<maciej.fijalkowski@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/3] Cleanup intel driver declarations
Date: Tue, 3 Sep 2024 14:18:16 -0700	[thread overview]
Message-ID: <921e5259-27f2-413d-9075-c5dd2576a66f@intel.com> (raw)
In-Reply-To: <20240903122234.964218-1-yuehaibing@huawei.com>



On 9/3/2024 5:22 AM, Yue Haibing wrote:
> 
> Yue Haibing (3):
>   iavf: Remove unused declarations
>   igb: Cleanup unused declarations
>   ice: Cleanup unused declarations
> 

It would be interesting to see when the code for these declarations was
removed (if it was ever present in the kernel to begin with?)

      parent reply	other threads:[~2024-09-03 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 12:22 [Intel-wired-lan] [PATCH net-next 0/3] Cleanup intel driver declarations Yue Haibing
2024-09-03 12:22 ` [Intel-wired-lan] [PATCH net-next 1/3] iavf: Remove unused declarations Yue Haibing
2024-09-03 12:22 ` [Intel-wired-lan] [PATCH net-next 2/3] igb: Cleanup " Yue Haibing
2024-09-03 12:22 ` [Intel-wired-lan] [PATCH net-next 3/3] ice: " Yue Haibing
2024-09-03 12:35 ` [Intel-wired-lan] [PATCH net-next 0/3] Cleanup intel driver declarations Fijalkowski, Maciej
2024-09-03 21:18 ` Jacob Keller [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=921e5259-27f2-413d-9075-c5dd2576a66f@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=ahmed.zaki@intel.com \
    --cc=amritha.nambiar@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=mateusz.polchlopek@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=yuehaibing@huawei.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