From: "David S. Miller" <davem@davemloft.net>
To: folkert@vanheusden.com
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] optimize check in port-allocation code
Date: Thu, 28 Apr 2005 12:08:24 -0700 [thread overview]
Message-ID: <20050428120824.6cc9b345.davem@davemloft.net> (raw)
In-Reply-To: <20050425061210.GB15167@vanheusden.com>
On Mon, 25 Apr 2005 08:12:13 +0200
folkert@vanheusden.com wrote:
> 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.
next prev parent reply other threads:[~2005-04-28 19:08 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 [this message]
2005-04-28 21:24 ` folkert
2005-05-03 21:36 ` David S. Miller
2005-05-04 7:15 ` folkert
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=20050428120824.6cc9b345.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=folkert@vanheusden.com \
--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).