From: David Miller <davem@davemloft.net>
To: arno@natisbad.org
Cc: netdev@vger.kernel.org, ben.thery@gmail.com
Subject: Re: [PATCH,RESEND] XFRM,IPv6: initialize ip6_dst_blackhole_ops.kmem_cachep
Date: Wed, 01 Oct 2008 06:23:44 -0700 (PDT) [thread overview]
Message-ID: <20081001.062344.250592216.davem@davemloft.net> (raw)
In-Reply-To: <87myhozd1n.fsf@natisbad.org>
From: arno@natisbad.org (Arnaud Ebalard)
Date: Wed, 01 Oct 2008 14:59:32 +0200
> David Miller <davem@davemloft.net> writes:
> >
> > Applied to net-2.6, thanks Arnaud!
>
> Can you queue it for -stable (2.6.26) too, if not already done?
Done.
prev parent reply other threads:[~2008-10-01 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:21 [PATCH] XFRM,IPv6: initialize ip6_dst_blackhole_ops.kmem_cachep Arnaud Ebalard
2008-09-25 9:21 ` Benjamin Thery
2008-09-25 9:38 ` Arnaud Ebalard
2008-10-01 9:26 ` [PATCH,RESEND] " Arnaud Ebalard
2008-10-01 9:38 ` David Miller
2008-10-01 12:59 ` Arnaud Ebalard
2008-10-01 13:23 ` David Miller [this message]
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=20081001.062344.250592216.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arno@natisbad.org \
--cc=ben.thery@gmail.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 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).