From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location
Date: Fri, 17 Jan 2020 21:59:43 +0000 [thread overview]
Message-ID: <7e2c22164e9949028d0b2d70ad970a9f@intel.com> (raw)
In-Reply-To: <20200116230610.1868-1-shiraz.saleem@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Shiraz Saleem
> Sent: Thursday, January 16, 2020 3:06 PM
> To: intel-wired-lan at lists.osuosl.org
> Cc: Saleem, Shiraz <shiraz.saleem@intel.com>
> Subject: [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location
>
> From: "Shiraz Saleem" <shiraz.saleem@intel.com>
>
> Move i40e_client.h to include/linux/net/intel/* since its shared between
> i40iw and i40e.
>
> Signed-off-by: Shiraz Saleem <shiraz.saleem@intel.com>
> ---
> drivers/infiniband/hw/i40iw/Makefile | 1 -
> drivers/infiniband/hw/i40iw/i40iw.h | 2 +-
> drivers/net/ethernet/intel/i40e/i40e.h | 2 +-
> drivers/net/ethernet/intel/i40e/i40e_client.c | 2 +-
> drivers/net/ethernet/intel/i40e/i40e_client.h | 203 --------------------------
> include/linux/net/intel/i40e_client.h | 203
> ++++++++++++++++++++++++++
> 6 files changed, 206 insertions(+), 207 deletions(-) delete mode 100644
> drivers/net/ethernet/intel/i40e/i40e_client.h
> create mode 100644 include/linux/net/intel/i40e_client.h
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2020-01-17 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 23:06 [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location Shiraz Saleem
2020-01-16 23:06 ` [Intel-wired-lan] [PATCH 2/2] i40e: Register a virtbus device to provide RDMA Shiraz Saleem
2020-01-17 22:02 ` Bowers, AndrewX
2020-01-17 21:59 ` Bowers, AndrewX [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-02 16:51 [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location Shiraz Saleem
2020-03-05 22:35 ` Bowers, AndrewX
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=7e2c22164e9949028d0b2d70ad970a9f@intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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