From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@sourceware.org
Subject: Patch_or_Contribution granted: [Bug 1001159] Fixes from FreeBSD IP Stack CVS
Date: Tue, 22 Feb 2011 04:34:00 -0000 [thread overview]
Message-ID: <20110222043409.E00452F78003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001159-0@http.bugs.ecos.sourceware.org/>
Jonathan Larmour <jifl@ecoscentric.com> has granted Patch_or_Contribution:
Bug 1001159: Fixes from FreeBSD IP Stack CVS
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001159
------- Additional Comments from Jonathan Larmour <jifl@ecoscentric.com>
Hi Kelvin,
Thanks for the patch! This looks good, although I think there should be two
minor changes:
- make CYGPKG_NET_TCP_REASS_DIVISOR be of "booldata" type, which means we can
eliminate CYGPKG_NET_TCP_REASS_LIMIT.
- make all the added queue limit stuff depend on this option being set.
Otherwise we're adding code (albeit small) which can never be used.
I'll attach the patch I'm committing now.
For the record, the bulk of these patches originate from FreeBSD, so there is
no need for a copyright assignment for the trivial stuff left over.
Jifl
parent reply other threads:[~2011-02-22 4:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-1001159-0@http.bugs.ecos.sourceware.org/>]
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=20110222043409.E00452F78003@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).