From: Karl Hiramoto <karl@hiramoto.org>
To: chas3@users.sourceforge.net
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [Linux-ATM-General] [PATCH] br2684 testing needed for packet loss and performance
Date: Sat, 29 Aug 2009 12:24:39 +0200 [thread overview]
Message-ID: <4A9901E7.9040804@hiramoto.org> (raw)
In-Reply-To: <200908281225.n7SCPUC3031293@cmf.nrl.navy.mil>
Chas Williams (CONTRACTOR) wrote:
> In message <4A97B3A9.6040103@hiramoto.org>,Karl Hiramoto writes:
>
>> Anyone care to test or comment on these patches? I've attached
>> versions for 2.6.28 and 2.6.30.
>>
>
> this needs to be against the net-2.6 git repository. but the 2.6.30
> would probably apply just fine.
Ok i will resend the patch against net-2.6 or should i do net-next-2.6?
Do i have to wait for a merge window?
> except for the comments, below this
> patch looks fine and makes sense. a similar thing had to be done for
> the lec.c interface.
>
>
Ok I'll clean up all these issues.
--
karl
next prev parent reply other threads:[~2009-08-29 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 10:38 [PATCH] br2684 testing needed for packet loss and performance Karl Hiramoto
2009-08-28 12:25 ` [Linux-ATM-General] " Chas Williams (CONTRACTOR)
2009-08-29 10:24 ` Karl Hiramoto [this message]
2009-08-29 11:24 ` [PATCH] atm/br2684: netif_stop_queue() when atm device busy and netif_wake_queue() when we can send packets again Karl Hiramoto
2009-08-31 14:29 ` Chas Williams (CONTRACTOR)
2009-09-03 6:27 ` David Miller
2009-09-03 13:44 ` Chas Williams (CONTRACTOR)
2009-09-10 19:49 ` [Linux-ATM-General] " Philip A. Prindeville
2009-09-10 21:30 ` Karl Hiramoto
2009-09-11 18:48 ` David Miller
2009-09-15 13:44 ` Karl Hiramoto
2009-09-15 14:57 ` Karl Hiramoto
2009-09-16 18:04 ` Philip A. Prindeville
2009-09-11 19:56 ` Philip A. Prindeville
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=4A9901E7.9040804@hiramoto.org \
--to=karl@hiramoto.org \
--cc=chas3@users.sourceforge.net \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@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).