From: Steffen Klassert <steffen.klassert@secunet.com>
To: Mathias Krause <minipli@googlemail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec 0/3] vti/vti6: minor tweaks + one fix
Date: Tue, 13 May 2014 10:41:14 +0200 [thread overview]
Message-ID: <20140513084114.GZ32371@secunet.com> (raw)
In-Reply-To: <1399671822-12842-1-git-send-email-minipli@googlemail.com>
On Fri, May 09, 2014 at 11:43:39PM +0200, Mathias Krause wrote:
> Hi Steffen,
>
> this series addresses a few issues related to VTI. The first patch fixes
> a bug in the vti6 module calling unregister_pernet_device() twice in the
> error path. That's probably material for ipsec.git.
> The second patch simplifies the error handling path in module init/fini
> of vti6. The third patch does the same for vti. Those two are probably
> material for ipsec-next.git as we're at -rc5 already. But I leave that
> decision to you.
Right, patches two and three should go to ipsec-next. But the second
patch does not apply without the first patch. Please send separate
patchsets for ipsec and ipsec-next in future.
Thanks!
next prev parent reply other threads:[~2014-05-13 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 21:43 [PATCH ipsec 0/3] vti/vti6: minor tweaks + one fix Mathias Krause
2014-05-09 21:43 ` [PATCH ipsec 1/3] vti6: Don't unregister pernet ops twice on init errors Mathias Krause
2014-05-13 8:35 ` Steffen Klassert
2014-05-09 21:43 ` [PATCH ipsec 2/3] vti6: Simplify error handling in module init and exit Mathias Krause
2014-05-09 21:43 ` [PATCH ipsec 3/3] vti: " Mathias Krause
2014-05-13 8:41 ` Steffen Klassert [this message]
2014-05-13 20:38 ` [PATCH ipsec 0/3] vti/vti6: minor tweaks + one fix Mathias Krause
2014-06-30 9:19 ` Steffen Klassert
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=20140513084114.GZ32371@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=minipli@googlemail.com \
--cc=netdev@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.