All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: Julian Anastasov <ja@ssi.bg>, lvs-devel@vger.kernel.org
Subject: Re: [PATCHv2 net-next] ipvs: avoid rcu_barrier during netns cleanup
Date: Fri, 11 Oct 2013 10:57:13 +0200	[thread overview]
Message-ID: <20131011085713.GA4166@localhost> (raw)
In-Reply-To: <20131011050558.GC4624@verge.net.au>

On Fri, Oct 11, 2013 at 02:05:58PM +0900, Simon Horman wrote:
> Thanks Julian.
> 
> Pablo, could you merge net-next into nf-next so that
> I can apply this patch on top of the later?
> 
> In particular I believe I need the following commit
> to allow Julian's patch to apply cleanly (at all).
> 
> bcbde4c ("ipvs: make the service replacement more robust")

Just refreshed my nf-next tree.

Please, let me know if you still need any further action from my side,
it may require pinging David to merge net into net-next.

  reply	other threads:[~2013-10-11  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  6:24 [PATCHv2 net-next] ipvs: avoid rcu_barrier during netns cleanup Julian Anastasov
2013-10-11  5:05 ` Simon Horman
2013-10-11  8:57   ` Pablo Neira Ayuso [this message]
2013-10-15  1:37     ` Simon Horman

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=20131011085713.GA4166@localhost \
    --to=pablo@netfilter.org \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@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.