From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH S29 04/14] i40e: Add a client definition of I40E_MAX_USER_PRIORITY
Date: Thu, 18 Feb 2016 22:38:50 -0800 [thread overview]
Message-ID: <1455863930.3128.67.camel@intel.com> (raw)
In-Reply-To: <1455754344-6372-5-git-send-email-avinash.dayanand@intel.com>
On Wed, 2016-02-17 at 16:12 -0800, Avinash Dayanand wrote:
> From: Catherine Sullivan <catherine.sullivan@intel.com>
>
> IWARP uses I40E_MAX_USER_PRIORITY in i40e_client.h but it is not
> defined
> there so add a I40E_CLIENT_MAX_USER_PRIORITY definition to
> i40e_client.h
> and a comment to i40e.h that we need to keep the two definitions
> synced.
>
>
> Signed-off-by: Catherine Sullivan <catherine.sullivan@intel.com>
> Change-ID: I0fc8868c2b090f54914ab738ec52b48ae4f523e2
> ---
> Testing Hints: Make sure it compiles.
>
> ?drivers/net/ethernet/intel/i40e/i40e.h | 3 +++
> ?1 file changed, 3 insertions(+)
Not sure how this got through review, but this should not be pushed
upstream. ?First the patch description (and code comment) refer to
i40e_client.h which does not exist in the Linux kernel AND this patch
is clearly iWARP related, so I am dropping this patch from the series.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160218/19f05950/attachment.asc>
next prev parent reply other threads:[~2016-02-19 6:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 0:12 [Intel-wired-lan] [next PATCH S29 00/14] i40e/i40evf updates Avinash Dayanand
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 01/14] i40e: Add functions to blink led on 10GBaseT PHY Avinash Dayanand
2016-02-18 17:18 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 02/14] i40e: Fix led blink capability for " Avinash Dayanand
2016-02-18 17:19 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 03/14] i40e: Increase timeout when checking GLGEN_RSTAT_DEVSTATE bit Avinash Dayanand
2016-02-18 18:22 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 04/14] i40e: Add a client definition of I40E_MAX_USER_PRIORITY Avinash Dayanand
2016-02-18 18:24 ` Bowers, AndrewX
2016-02-19 6:38 ` Jeff Kirsher [this message]
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 05/14] i40e: Do not wait for Rx queue disable in DCB reconfig Avinash Dayanand
2016-02-18 19:00 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 06/14] i40e: Fix for unexpected messaging Avinash Dayanand
2016-02-18 19:04 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 07/14] i40e: Expose some registers to program parser, FD and RSS logic Avinash Dayanand
2016-02-18 19:07 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 08/14] i40e: Fix PSOD's when npar enabled Avinash Dayanand
2016-02-18 0:35 ` Brandeburg, Jesse
2016-02-18 4:00 ` Jeff Kirsher
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 09/14] i40e: add adminq commands for rx ctl registers Avinash Dayanand
2016-02-19 0:39 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 10/14] i40e: implement and use rx ctl helper functions Avinash Dayanand
2016-02-19 0:40 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 11/14] i40e: Use the new rx ctl register helpers. Don't use AQ calls from clear_hw Avinash Dayanand
2016-02-19 0:40 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 12/14] i40e: Fix for the NPAR PSOD issue Avinash Dayanand
2016-02-18 0:36 ` Brandeburg, Jesse
2016-02-18 4:01 ` Jeff Kirsher
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 13/14] i40e: let go of the past Avinash Dayanand
2016-02-18 23:10 ` Bowers, AndrewX
2016-02-18 0:12 ` [Intel-wired-lan] [next PATCH S29 14/14] i40e/i40evf: Bump i40e to 1.4.25 and i40evf to 1.4.15 Avinash Dayanand
2016-02-18 23:13 ` 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=1455863930.3128.67.camel@intel.com \
--to=jeffrey.t.kirsher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.