From: Jeff Garzik <jgarzik@pobox.com>
To: Radheka Godse <radheka.godse@intel.com>, mitch.a.williams@intel.com
Cc: fubar@us.ibm.com, bonding-devel@lists.sourceforge.net,
netdev@oss.sgi.com
Subject: Re: [PATCH 2.6.13-rc1 0/17] bonding: Sysfs Support
Date: Sun, 31 Jul 2005 01:28:05 -0400 [thread overview]
Message-ID: <42EC6165.2080809@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507011313500.17459@localhost.localdomain>
Radheka Godse wrote:
> This patch set is an updated sysfs bonding patch to the one sent
> previously in April. The patch is upto date with all recent bonding
> and kernel changes and applies cleanly to linux-2.6.13-rc1. It adds
> sysfs entry for the "Xmit Hash Policy" for new bonding module param;
> incorporates feedback and bug fixes on all known issues and has been
> tested on linux-2.6.13-rc1.
Will we be seeing a resend of this patch series, incorporating the
comments from GregKH and others?
Jeff
prev parent reply other threads:[~2005-07-31 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 20:22 [PATCH 2.6.13-rc1 0/17] bonding: Sysfs Support Radheka Godse
2005-07-31 5:28 ` Jeff Garzik [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=42EC6165.2080809@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@oss.sgi.com \
--cc=radheka.godse@intel.com \
/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).