From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>
Subject: Re: linux-next: build failure after merge of most of the trees
Date: Fri, 29 May 2015 10:34:59 +1000 [thread overview]
Message-ID: <20150529103459.4e90212d@canb.auug.org.au> (raw)
In-Reply-To: <1432826811.7456.10.camel@edumazet-glaptop2.roam.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Hi Eric,
On Thu, 28 May 2015 08:26:51 -0700 Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> We were alerted of this problem thanks to kbuild test robot.
>
> This fix is not a definitive one I hope.
No, just something to allow me to get my tree to build so I could go to
bed :-)
> Golden rule is that vmalloc() users must include vmalloc.h themselves,
> not by an indirect include.
Yep, that is a special case of Rule 1.
> I sent one fix, and prepared others, but I prefer that each offender is
> fixed.
Yeah, thanks to Dave for that.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-29 0:34 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 [this message]
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
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=20150529103459.4e90212d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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).