From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, e1000-devel@lists.sourceforge.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux.nics@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [linux-nics] linux-next: Tree for Aug 11 (net/ethernet/intel/i40e)
Date: Mon, 11 Aug 2014 12:53:06 -0700 [thread overview]
Message-ID: <1407786786.2189.0.camel@jtkirshe-mobl.jf.intel.com> (raw)
In-Reply-To: <53E8ECA9.6060806@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Mon, 2014-08-11 at 09:17 -0700, Randy Dunlap wrote:
> On 08/10/14 22:52, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add code intended for v3.18 until after v3.17-rc1 is
> > released.
> >
> > Changes since 20140808:
> >
>
> on i386 and x86_64:
>
> ../drivers/net/ethernet/intel/i40e/i40e_fcoe.c: In function
> 'i40e_get_fcoe_tc_map':
> ../drivers/net/ethernet/intel/i40e/i40e_fcoe.c:354:23: error:
> 'IEEE_8021QAZ_APP_SEL_ETHERTYPE' undeclared (first use in this
> function)
> if (app.selector == IEEE_8021QAZ_APP_SEL_ETHERTYPE &&
>
>
> Needs to #include <uapi/linux/dcbnl.h> ??
Yeah, Dave has already accepted a patch to resolve that, which I believe
went into his net tree.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-11 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140811155213.0aa083ce@canb.auug.org.au>
2014-08-11 16:17 ` linux-next: Tree for Aug 11 (net/ethernet/intel/i40e) Randy Dunlap
2014-08-11 19:53 ` Jeff Kirsher [this message]
2014-08-11 21:54 ` [linux-nics] " David Miller
2014-08-11 22:16 ` Jeff Kirsher
2014-08-11 22:20 ` 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=1407786786.2189.0.camel@jtkirshe-mobl.jf.intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).