From: Jeff Garzik <jgarzik@pobox.com>
To: Amir Noam <amir.noam@intel.com>
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [PATCH 0/10] [bonding 2.6] propagating master's settings to slaves
Date: Thu, 11 Sep 2003 10:55:24 -0400 [thread overview]
Message-ID: <3F608CDC.4020103@pobox.com> (raw)
In-Reply-To: <200309111737.15424.amir.noam@intel.com>
Amir Noam wrote:
> The following set ports to 2.6 the propagation patch set that went into
> 2.4.23-pre3. Also, fix a free_netdev() error that the previous patch set
> introduced and fix a compile error using ipx_hdr().
Thanks!
> Patches should be applied after the previous patch set (sent 2003/09/04)
> that ported bug fixes from 2.4.
Today is my work-at-home day, and I was actually putting these ("these"
== previous patch set you mention) in my queue right now. Hopefully I
can get to this new set today as well.
Jeff
next prev parent reply other threads:[~2003-09-11 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:37 [PATCH 0/10] [bonding 2.6] propagating master's settings to slaves Amir Noam
2003-09-11 14:55 ` Jeff Garzik [this message]
2003-09-11 18:58 ` Jeff Garzik
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=3F608CDC.4020103@pobox.com \
--to=jgarzik@pobox.com \
--cc=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.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).