From: Jeff Garzik <jgarzik@pobox.com>
To: Shmuel Hen <shmulik.hen@intel.com>
Cc: "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, bonding-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/6][8021q][2.4] Use VLAN tag set functionality in 8021q module
Date: Mon, 26 Jan 2004 12:42:53 -0500 [thread overview]
Message-ID: <4015519D.5080803@pobox.com> (raw)
In-Reply-To: <200401261522.14126.shmulik.hen@intel.com>
Shmuel Hen wrote:
> Also, speaking of the bonding changes queued in netdev-2.4, some of
> those have been queued there since 2.4.23 came out. Will those be
> pushed to Marcelo during 2.4.25 or do you intend to hold them until
> 2.4.26-preX starts?
Sounds like DaveM and I will need to coordinate a bit, then.
Queued bonding stuff for 2.4: Marcelo wanted to wait until 2.4.25
release, so they will go to Marcelo for 2.4.26-pre1.
Queued bonding stuff for 2.6: Similar picture. Waiting for 2.6.2
release, then it goes to Andrew/Linus.
Note that at some point, IMO you need to plan on 2.6-only development,
since keeping bonding the same in 2.4 and 2.6 -through ABI changes- may
not be feasible past the short term. 2.4 developmnent is intentionally
slowing down on Marcelo's side, even though vendors are still shipping
2.4.x stuff.
Jeff
next prev parent reply other threads:[~2004-01-26 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A02A46612@hasmsx403.iil.intel.com>
2004-01-26 13:22 ` [PATCH 3/6][8021q][2.4] Use VLAN tag set functionality in 8021q module Shmuel Hen
2004-01-26 17:42 ` Jeff Garzik [this message]
[not found] <E791C176A6139242A988ABA8B3D9B38A03A9CCD5@hasmsx403.iil.intel.com>
2004-01-28 16:57 ` Shmuel Hen
2004-01-28 19:40 ` David S. Miller
2004-01-25 12:28 Hen, Shmulik
2004-01-26 5:34 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:57 Shmuel Hen
2004-01-22 18:06 ` David S. Miller
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=4015519D.5080803@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.