From: "David S. Miller" <davem@redhat.com>
To: Shmuel Hen <shmulik.hen@intel.com>
Cc: jgarzik@pobox.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: Wed, 28 Jan 2004 11:40:47 -0800 [thread overview]
Message-ID: <20040128114047.3d5e8817.davem@redhat.com> (raw)
In-Reply-To: <200401281857.25642.shmulik.hen@intel.com>
On Wed, 28 Jan 2004 18:57:25 +0200
Shmuel Hen <shmulik.hen@intel.com> wrote:
> On Monday 26 January 2004 19:42, Jeff Garzik wrote:
> > 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.
>
> By coordinate, do you mean that you'll take in all of our patches and
> forward them to Dave at the appropriate time, or instead wait for
> Dave to take in the first half (which is not bonding specific) and
> only then take the last half ?
I think the best is to have me push the infrastructure into 2.6.3-pre1
and then Jeff can add the bonding bits to his tree.
next prev parent reply other threads:[~2004-01-28 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A03A9CCD5@hasmsx403.iil.intel.com>
2004-01-28 16:57 ` [PATCH 3/6][8021q][2.4] Use VLAN tag set functionality in 8021q module Shmuel Hen
2004-01-28 19:40 ` David S. Miller [this message]
[not found] <E791C176A6139242A988ABA8B3D9B38A02A46612@hasmsx403.iil.intel.com>
2004-01-26 13:22 ` Shmuel Hen
2004-01-26 17:42 ` Jeff Garzik
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=20040128114047.3d5e8817.davem@redhat.com \
--to=davem@redhat.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.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 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).