From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: ap@cipherica.com, netdev@oss.sgi.com
Subject: Re: [PATCH] more improvement to dev_alloc_name -- strnchr
Date: Mon, 19 Jan 2004 21:25:37 -0800 [thread overview]
Message-ID: <20040119212537.5d73a031.davem@redhat.com> (raw)
In-Reply-To: <20040119113204.5913a8d6.shemminger@osdl.org>
On Mon, 19 Jan 2004 11:32:04 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:
> Okay, this patch avoids the loop if no wildcarding present, and keeps
> the same behaviour as original. It adds the string function strnchr
> to avoid searching past the maximum ifname size to find the format character.
I'm deferring this until the next 2.6.x-pre starts up as well.
Please resend at that time.
Thanks Stephen.
prev parent reply other threads:[~2004-01-20 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1074302619.40088e9bd44a6@www.geekmail.cc>
2004-01-19 19:32 ` [PATCH] more improvement to dev_alloc_name -- strnchr Stephen Hemminger
2004-01-19 20:06 ` Andi Kleen
2004-01-19 21:07 ` Stephen Hemminger
2004-01-19 21:15 ` Andi Kleen
2004-01-19 21:44 ` David S. Miller
2004-01-19 23:27 ` Alex Pankratov
2004-01-20 5:25 ` David S. Miller [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=20040119212537.5d73a031.davem@redhat.com \
--to=davem@redhat.com \
--cc=ap@cipherica.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).