All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	kernel@pengutronix.de
Subject: Re: [PATCH bluetooth-next] 6lowpan: add request for ipv6 module
Date: Mon, 22 Jun 2015 10:31:43 +0300	[thread overview]
Message-ID: <1434958303.2794.26.camel@linux.intel.com> (raw)
In-Reply-To: <1434899479-22310-1-git-send-email-alex.aring@gmail.com>

Hi Alex,

On su, 2015-06-21 at 17:11 +0200, Alexander Aring wrote:
> The iphc module depends on CONFIG_IPV6, because it's not very useful to
> build the module without IPv6 support. Recently an user reported about
> issues for setting an IPv6 address to a 6LoWPAN interface. The issues
> was solved by modprobe the ipv6 module before. To avoid such user issues
> we try to request the ipv6 module when the 6LoWPAN module is loaded.
> 
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
>  net/6lowpan/iphc.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/6lowpan/iphc.c b/net/6lowpan/iphc.c
> index 94a375c..9055d7b 100644
> --- a/net/6lowpan/iphc.c
> +++ b/net/6lowpan/iphc.c
> @@ -613,6 +613,8 @@ EXPORT_SYMBOL_GPL(lowpan_header_compress);
>  
>  static int __init lowpan_module_init(void)
>  {
> +	request_module_nowait("ipv6");
> +
>  	request_module_nowait("nhc_dest");
>  	request_module_nowait("nhc_fragment");
>  	request_module_nowait("nhc_hop");


Acked-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>



Cheers,
Jukka


--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in

  reply	other threads:[~2015-06-22  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21 15:11 [PATCH bluetooth-next] 6lowpan: add request for ipv6 module Alexander Aring
2015-06-22  7:31 ` Jukka Rissanen [this message]
2015-06-22 10:24 ` Marcel Holtmann

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=1434958303.2794.26.camel@linux.intel.com \
    --to=jukka.rissanen@linux.intel.com \
    --cc=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@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 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.