From: Mitchell Blank Jr <mitch@sfgoth.com>
To: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Cc: Jeff Garzik <jeff@garzik.org>, Netdev List <netdev@vger.kernel.org>
Subject: Re: ATM bug found
Date: Sun, 1 Oct 2006 08:38:42 -0700 [thread overview]
Message-ID: <20061001153842.GD83074@gaz.sfgoth.com> (raw)
In-Reply-To: <200610011514.k91FE3ai003599@cmf.nrl.navy.mil>
chas williams - CONTRACTOR wrote:
> still generates a warning from gcc though.
The warning is bogus in this case, though -- the only way for "*pcr" to
be unset is when alloc_shaper() returns non-zero
> + *pcr = 0;
You're right, 0 is better than ATM_MAX_PCR here.
-Mitch
prev parent reply other threads:[~2006-10-01 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 13:24 ATM bug found Jeff Garzik
2006-10-01 14:58 ` Mitchell Blank Jr
2006-10-01 15:22 ` chas williams - CONTRACTOR
2006-10-01 15:14 ` chas williams - CONTRACTOR
2006-10-01 15:38 ` Mitchell Blank Jr [this message]
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=20061001153842.GD83074@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--cc=chas@cmf.nrl.navy.mil \
--cc=jeff@garzik.org \
--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 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.