netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, edumazet@google.com
Subject: Re: linux-next: build failure after merge of most of the trees
Date: Fri, 29 May 2015 10:36:45 +1000	[thread overview]
Message-ID: <20150529103645.57579e82@canb.auug.org.au> (raw)
In-Reply-To: <20150528.114203.717794268051352731.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

Hi Dave,

On Thu, 28 May 2015 11:42:03 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>
> The only thing I will say on this matter is that the _only_ way this
> problem will go away is if someone does the work necessary to get rid
> of that implicit vmalloc.h include that happens on all x86 platform
> builds.
> 
> So if you want this to stop happening, work on that.

I may have a look in my (copious) free time :-)

> I've applied the following to net-next, thanks for your report.

Thanks for that.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-05-29  0:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 12:06 linux-next: build failure after merge of most of the trees Stephen Rothwell
2015-05-28 15:26 ` Eric Dumazet
2015-05-29  0:34   ` Stephen Rothwell
2015-05-28 18:42 ` David Miller
2015-05-28 18:51   ` Joe Perches
2015-05-28 21:35     ` David Miller
2015-05-28 22:13       ` Eric Dumazet
2015-05-29  0:36   ` Stephen Rothwell [this message]

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=20150529103645.57579e82@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).