linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Anderson Briglia <anderson.briglia@openbossa.org>,
	Anderson Lizardo <anderson.lizardo@openbossa.org>,
	Bruna Moreira <bruna.moreira@openbossa.org>,
	Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the wireless tree
Date: Tue, 28 Jun 2011 15:11:15 -0300	[thread overview]
Message-ID: <20110628181115.GB23183@joana> (raw)
In-Reply-To: <20110623130317.b3a6085e.sfr@canb.auug.org.au>

Hi John,

* Stephen Rothwell <sfr@canb.auug.org.au> [2011-06-23 13:03:17 +1000]:

> Hi John,
> 
> After merging the wireless tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> net/bluetooth/smp.c: In function 'smp_e':
> net/bluetooth/smp.c:49:21: error: storage size of 'sg' isn't known
> net/bluetooth/smp.c:67:2: error: implicit declaration of function 'sg_init_one'
> net/bluetooth/smp.c:49:21: warning: unused variable 'sg'
> 
> Caused by commit d22ef0bc83c5 ("Bluetooth: Add LE SMP Cryptoolbox
> functions").  Missing include file, presumably.  This batch has been in
> the bluetooth tree since June 14, so it may have been exposed by the
> removal of linux/mm.h from netdevice.h ...
> 
> I have added the following patch as a merge fix up for today.
> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 23 Jun 2011 12:58:55 +1000
> Subject: [PATCH] Bluetooth: include scatterlist.h where needed
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  net/bluetooth/smp.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/net/bluetooth/smp.c b/net/bluetooth/smp.c
> index 52e9ec2..a36f870 100644
> --- a/net/bluetooth/smp.c
> +++ b/net/bluetooth/smp.c
> @@ -25,6 +25,7 @@
>  #include <net/bluetooth/l2cap.h>
>  #include <net/bluetooth/smp.h>
>  #include <linux/crypto.h>
> +#include <linux/scatterlist.h>
>  #include <crypto/b128ops.h>

Thanks for pick this patch to wireless tree ;) 

	Gustavo

  parent reply	other threads:[~2011-06-28 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  3:03 linux-next: build failure after merge of the wireless tree Stephen Rothwell
2011-06-23  3:46 ` David Miller
2011-06-28 18:11 ` Gustavo F. Padovan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-12  2:36 Stephen Rothwell
2011-05-16  2:02 Stephen Rothwell
2011-05-16 18:08 ` John W. Linville
2010-06-23  2:51 Stephen Rothwell
2010-06-23 14:57 ` John W. Linville
2010-03-10  3:36 Stephen Rothwell
2010-03-10  5:53 ` Juuso Oikarinen
2010-03-10 11:19   ` Luciano Coelho

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=20110628181115.GB23183@joana \
    --to=padovan@profusion.mobi \
    --cc=adobriyan@gmail.com \
    --cc=anderson.briglia@openbossa.org \
    --cc=anderson.lizardo@openbossa.org \
    --cc=bruna.moreira@openbossa.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vinicius.gomes@openbossa.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).