From: David Miller <davem@davemloft.net>
To: dlezcano@fr.ibm.com
Cc: yoshfuji@linux-ipv6.org, pekkas@netcore.fi, netdev@vger.kernel.org
Subject: Re: [patch 5/5] ipv6: make the protocol initialization to return an error code
Date: Tue, 11 Dec 2007 02:25:52 -0800 (PST) [thread overview]
Message-ID: <20071211.022552.157588535.davem@davemloft.net> (raw)
In-Reply-To: <20071210151440.241406358@ICON-9-164-138-215.megacenter.de.ibm.com>
From: Daniel Lezcano <dlezcano@fr.ibm.com>
Date: Mon, 10 Dec 2007 16:09:15 +0100
> This patchset makes the different protocols to return an error code, so
> the af_inet6 module can check the initialization was correct or not.
>
> The raw6 was taken into account to be consistent with the rest of the
> protocols, but the registration is at the same place.
> Because the raw6 has its own init function, the proto and the ops structure
> can be moved inside the raw6.c file.
>
> Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
Also applied, thanks Daniel.
next prev parent reply other threads:[~2007-12-11 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 15:09 [patch 0/5] ipv6: make af_inet6 subsystems to return an error at init Daniel Lezcano
2007-12-10 15:09 ` [patch 1/5] ipv6: make flowlabel to return an error Daniel Lezcano
2007-12-11 10:23 ` David Miller
2007-12-10 15:09 ` [patch 2/5] ipv6: make extended headers to return an error at initialization Daniel Lezcano
2007-12-11 10:24 ` David Miller
2007-12-10 15:09 ` [patch 3/5] ipv6: make frag " Daniel Lezcano
2007-12-11 10:24 ` David Miller
2007-12-10 15:09 ` [patch 4/5] ipv6: make inet6_register_protosw to return an error code Daniel Lezcano
2007-12-11 10:25 ` David Miller
2007-12-10 15:09 ` [patch 5/5] ipv6: make the protocol initialization " Daniel Lezcano
2007-12-11 10:25 ` David Miller [this message]
2007-12-10 15:32 ` [patch 0/5] ipv6: make af_inet6 subsystems to return an error at init Daniel Lezcano
2007-12-11 0:45 ` David Miller
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=20071211.022552.157588535.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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).