mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: sfr@canb.auug.org.au, 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: Thu, 28 May 2015 14:35:45 -0700 (PDT)	[thread overview]
Message-ID: <20150528.143545.1946361377143498741.davem@davemloft.net> (raw)
In-Reply-To: <1432839075.1556.4.camel@perches.com>

From: Joe Perches <joe@perches.com>
Date: Thu, 28 May 2015 11:51:15 -0700

> On Thu, 2015-05-28 at 11:42 -0700, David Miller wrote:
>> I've applied the following to net-next, thanks for your report.
>> 
>> ====================
>> [PATCH] treewide: Add missing vmalloc.h inclusion.
>> 
>> All of these files were only building on non-x86 because of
>> the indirect of inclusion of vmalloc.h by, of all things,
>> "net/inet_hashtables.h"
> []
>> diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c
> []
>> @@ -444,6 +444,7 @@ static int skcipher_recvmsg(struct kiocb *unused, struct socket *sock,
>>  			err = skcipher_wait_for_data(sk, flags);
>>  			if (err)
>>  				goto unlock;
>> +			used = ctx->used;
> 
> huh?

Bogus chunk in my local tree, didn't make it into the final commit I
pushed out.

But thanks for noticing.

  reply	other threads:[~2015-05-28 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 12:06 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 [this message]
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=20150528.143545.1946361377143498741.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.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

all inboxes | Powered by JetHome®