netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, pekkas@netcore.fi,
	netdev@vger.kernel.org
Subject: Re: [patch 0/5] ipv6:  make af_inet6 subsystems to return an error at init
Date: Mon, 10 Dec 2007 16:32:50 +0100	[thread overview]
Message-ID: <475D5C22.1090103@fr.ibm.com> (raw)
In-Reply-To: <20071210150910.440970057@ICON-9-164-138-215.megacenter.de.ibm.com>

Daniel Lezcano wrote:
> This patchset continue the work to make the different af_inet6 
> subsystems initialization functions to return an error code and
> to handle the error to fails safely.
> 
> It takes into account:
> 	* flowlabel
> 	* exthdrs
> 	* frag
> 	* udp
> 	* udplite
> 	* tcp
> 	* raw

I just noticed that I forgot to put ipv6 under bracket.
Sorry for that :(

Should I resend the patchset ?

  parent reply	other threads:[~2007-12-10 15:36 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
2007-12-10 15:32 ` Daniel Lezcano [this message]
2007-12-11  0:45   ` [patch 0/5] ipv6: make af_inet6 subsystems to return an error at init 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=475D5C22.1090103@fr.ibm.com \
    --to=dlezcano@fr.ibm.com \
    --cc=davem@davemloft.net \
    --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).