From: Greg KH <greg@kroah.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: stable@vger.kernel.org, Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
Neil Horman <nhorman@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: Bonding fixes for 2.6.33.y
Date: Wed, 30 Nov 2011 07:49:09 +0900 [thread overview]
Message-ID: <20111129224909.GA27909@kroah.com> (raw)
In-Reply-To: <1322533200.26733.15.camel@bwh-desktop>
On Tue, Nov 29, 2011 at 02:19:59AM +0000, Ben Hutchings wrote:
> These have been applied to 2.6.32.y but are missing from 2.6.33.y:
Perhaps because 2.6.33.y is not end-of-life and is not having any more
releases?
sorry,
greg k-h
next prev parent reply other threads:[~2011-11-29 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 2:19 Bonding fixes for 2.6.33.y Ben Hutchings
2011-11-29 22:49 ` Greg KH [this message]
2011-11-29 23:46 ` Josh Boyer
2011-11-30 0:15 ` Greg KH
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=20111129224909.GA27909@kroah.com \
--to=greg@kroah.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=stable@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).