From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: John Fastabend <john.fastabend@gmail.com>, jhs@mojatatu.com
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [net-next PATCH 1/2] ixgbe: use u32 instead of __u32 in model header
Date: Wed, 17 Feb 2016 14:41:48 -0800 [thread overview]
Message-ID: <1455748908.2958.22.camel@intel.com> (raw)
In-Reply-To: <20160217223453.9858.76096.stgit@john-Precision-Tower-5810>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Wed, 2016-02-17 at 14:34 -0800, John Fastabend wrote:
> I incorrectly used __u32 types where we should be using u32 types
> when
> I added the ixgbe_model.h file.
>
> Fixes: 9d35cf062e05 ("net: ixgbe: add minimal parser details for
> ixgbe")
> Suggested-by: Jamal Hadi Salim <jhs@mojatatu.com>
> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_model.h | 18 +++++++++-----
> ----
> 1 file changed, 9 insertions(+), 9 deletions(-)
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Dave feel free to pull this series in from John to fix the issues with
his previous series.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-17 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 22:34 [net-next PATCH 1/2] ixgbe: use u32 instead of __u32 in model header John Fastabend
2016-02-17 22:35 ` [net-next PATCH 2/2] ixgbe: fix dates on header of ixgbe_model.h John Fastabend
2016-02-17 22:42 ` Jeff Kirsher
2016-02-18 2:44 ` David Miller
2016-02-17 22:41 ` Jeff Kirsher [this message]
2016-02-18 2:23 ` [net-next PATCH 1/2] ixgbe: use u32 instead of __u32 in model header David Miller
2016-02-18 2:44 ` David Miller
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=1455748908.2958.22.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.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).