From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] i40evf: fix 32 bit build warnings
Date: Tue, 13 Oct 2015 11:59:14 -0700 [thread overview]
Message-ID: <1444762754.2870.30.camel@intel.com> (raw)
In-Reply-To: <57023416.17EujnXPCo@wuerfel>
On Tue, 2015-10-13 at 13:37 +0200, Arnd Bergmann wrote:
> This is the majority of all build warnings we get on allmodconfig
> (both i386 and arm),
> so it would be really nice to have it fixed before 4.3. For all I can
> tell, the
> patch still applies on your branch too, but see below for the rebased
> version.
>
> I also note that your branch is not part of linux-next, is that
> intentional?
No, I assume it is because the linux-next maintainer has not picked up
my tree.
-------------- 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/20151013/c0a35e72/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
kbuild-all@01.org, Andrew Bowers <andrewx.bowers@intel.com>,
Shannon Nelson <shannon.nelson@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Matthew Vick <matthew.vick@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Mitch Williams <mitch.a.williams@intel.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] i40evf: fix 32 bit build warnings
Date: Tue, 13 Oct 2015 11:59:14 -0700 [thread overview]
Message-ID: <1444762754.2870.30.camel@intel.com> (raw)
In-Reply-To: <57023416.17EujnXPCo@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On Tue, 2015-10-13 at 13:37 +0200, Arnd Bergmann wrote:
> This is the majority of all build warnings we get on allmodconfig
> (both i386 and arm),
> so it would be really nice to have it fixed before 4.3. For all I can
> tell, the
> patch still applies on your branch too, but see below for the rebased
> version.
>
> I also note that your branch is not part of linux-next, is that
> intentional?
No, I assume it is because the linux-next maintainer has not picked up
my tree.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-13 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 20:13 [Intel-wired-lan] [PATCH] i40evf: fix 32 bit build warnings Arnd Bergmann
2015-10-07 20:13 ` Arnd Bergmann
2015-10-09 22:31 ` [Intel-wired-lan] " Jesse Brandeburg
2015-10-09 22:31 ` Jesse Brandeburg
2015-10-13 6:18 ` [Intel-wired-lan] " Jeff Kirsher
2015-10-13 6:18 ` Jeff Kirsher
2015-10-13 11:37 ` [Intel-wired-lan] " Arnd Bergmann
2015-10-13 11:37 ` Arnd Bergmann
2015-10-13 18:59 ` Jeff Kirsher [this message]
2015-10-13 18:59 ` Jeff Kirsher
2015-10-13 19:05 ` [Intel-wired-lan] " Jeff Kirsher
2015-10-13 19:05 ` Jeff Kirsher
2015-10-13 19:33 ` [Intel-wired-lan] " Jesse Brandeburg
2015-10-13 19:33 ` Jesse Brandeburg
2015-10-13 19:25 ` [Intel-wired-lan] " Jesse Brandeburg
2015-10-13 19:25 ` Jesse Brandeburg
2015-10-13 19:48 ` [Intel-wired-lan] " Arnd Bergmann
2015-10-13 19:48 ` Arnd Bergmann
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=1444762754.2870.30.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.