From: Patrick McHardy <kaber@trash.net>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
Julian Anastasov <ja@ssi.bg>, Patrick Schaaf <netdev@bof.de>
Subject: Re: [GIT PULL nf-next-2.6] IPVS
Date: Wed, 16 Feb 2011 14:19:58 +0100 [thread overview]
Message-ID: <4D5BCEFE.80106@trash.net> (raw)
In-Reply-To: <1297836293-5942-1-git-send-email-horms@verge.net.au>
On 16.02.2011 07:04, Simon Horman wrote:
> Hi Patrick,
>
> please consider pulling
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/lvs-test-2.6.git master
> go get:
>
> * Removal of unused ICMP code by Julian
> * More informative "no destination available" messages
> by Patrick Schaaf
> * Fix to buffering of synchronisation messages
> by Tinggong Wang and Julian
>
Pulled, thanks Simon.
next prev parent reply other threads:[~2011-02-16 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:04 [GIT PULL nf-next-2.6] IPVS Simon Horman
2011-02-16 6:04 ` [PATCH 1/3] ipvs: fix timer in get_curr_sync_buff Simon Horman
2011-02-16 6:04 ` [PATCH 2/3] ipvs: remove extra lookups for ICMP packets Simon Horman
2011-02-16 6:04 ` [PATCH 3/3] ipvs: make "no destination available" message more informative Simon Horman
2011-02-16 13:19 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-05 3:22 [GIT PULL nf-next-2.6] IPVS Simon Horman
2011-04-05 10:18 ` Patrick McHardy
2011-03-15 5:27 Simon Horman
2011-03-15 12:16 ` Patrick McHardy
2011-03-14 9:06 Simon Horman
2011-03-13 22:44 Simon Horman
2011-03-14 18:17 ` Patrick McHardy
2011-03-14 23:13 ` Simon Horman
2011-02-25 2:43 Simon Horman
2011-02-27 15:25 ` Patrick McHardy
2011-02-07 9:19 Simon Horman
2011-02-09 7:06 ` Patrick McHardy
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=4D5BCEFE.80106@trash.net \
--to=kaber@trash.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@bof.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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 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).