From: folkert@vanheusden.com
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] optimize check in port-allocation code
Date: Wed, 4 May 2005 09:15:20 +0200 [thread overview]
Message-ID: <20050504071516.GA1008@vanheusden.com> (raw)
In-Reply-To: <20050503143620.43cac50f.davem@davemloft.net>
> > > > I'll resend it as an attachment (see attachment).
> > > It still has spaces where there should be tabs, even though
> > > you compressed the patch and used attachment.
> > > The diff itself must already be corrupt before you attach
> > > it.
> > > Please double check that the patch you submit actually apply,
> > > this will save me a lot of wasted time.
> > Ok, I've redone them and tested if they patch cleanly, they now do.
> > See them attached.
> Both patches applied, thanks a lot.
What about moving that rover++ to the end of the loop? Was my
analysis correct?
Folkert van Heusden
--
Auto te koop, zie: http://www.vanheusden.com/daihatsu.php
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden.
--------------------------------------------------------------------
UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)
a try, it brings monitoring logfiles to a different level! See
http://vanheusden.com/multitail/features.html for a feature-list.
--------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE
Get your PGP/GPG key signed at www.biglumber.com!
prev parent reply other threads:[~2005-05-04 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 18:44 [PATCH] optimize check in port-allocation code folkert
[not found] ` <20050424190427.11b4863e.davem@davemloft.net>
[not found] ` <20050425061210.GB15167@vanheusden.com>
2005-04-28 19:08 ` David S. Miller
2005-04-28 21:24 ` folkert
2005-05-03 21:36 ` David S. Miller
2005-05-04 7:15 ` folkert [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=20050504071516.GA1008@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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).