From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<jeffrey.t.kirsher@intel.com>
Subject: Re: [RFC PATCH net-next v1 00/14] rename and shrink i40evf
Date: Fri, 14 Sep 2018 11:55:32 -0700 [thread overview]
Message-ID: <20180914115532.0000493b@intel.com> (raw)
In-Reply-To: <20180914043917.GB24996@f2>
On Fri, 14 Sep 2018 13:39:17 +0900 Benjamin wrote:
> > Jesse Brandeburg (14):
> > intel-ethernet: rename i40evf to iavf
>
> Seems like patch 1 didn't make it to netdev
> https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20180910/014025.html
Hi Ben, Thanks for the note, I don't know why it didn't show up for
you, it's here if you want to take a look:
https://patchwork.ozlabs.org/patch/969557/
next prev parent reply other threads:[~2018-09-15 0:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 22:31 [RFC PATCH net-next v1 00/14] rename and shrink i40evf Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 02/14] iavf: diet and reformat Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 03/14] iavf: rename functions and structs to new name Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 04/14] iavf: rename i40e_status to iavf_status Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 05/14] iavf: move i40evf files to new name Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 06/14] iavf: remove references to old names Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 07/14] iavf: rename device ID defines Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 08/14] iavf: rename I40E_ADMINQ_DESC Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 09/14] iavf: rename i40e_hw to iavf_hw Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 10/14] iavf: replace i40e_debug with iavf version Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 11/14] iavf: tracing infrastructure rename Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 12/14] iavf: rename most of i40e strings Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 13/14] iavf: finish renaming files to iavf Jesse Brandeburg
2018-09-13 22:31 ` [RFC PATCH net-next v1 14/14] intel-ethernet: use correct module license Jesse Brandeburg
2018-09-13 22:43 ` [RFC PATCH net-next v1 00/14] rename and shrink i40evf David Miller
2018-09-14 4:39 ` Benjamin Poirier
2018-09-14 18:55 ` Jesse Brandeburg [this message]
2018-09-14 9:10 ` Or Gerlitz
2018-09-14 19:17 ` Jesse Brandeburg
2018-09-21 13:51 ` Or Gerlitz
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=20180914115532.0000493b@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=benjamin.poirier@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@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;
as well as URLs for NNTP newsgroup(s).