From: David Miller <davem@davemloft.net>
To: opurdila@ixiacom.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH] net: device name allocation cleanups
Date: Wed, 18 Nov 2009 05:07:49 -0800 (PST) [thread overview]
Message-ID: <20091118.050749.39851073.davem@davemloft.net> (raw)
In-Reply-To: <200911181436.59261.opurdila@ixiacom.com>
From: Octavian Purdila <opurdila@ixiacom.com>
Date: Wed, 18 Nov 2009 14:36:59 +0200
> Thanks for your help ! Here is a new version which addresses the spotted issues:
>
> [net-next-2.6 PATCH] net: device name allocation cleanups
>
> Signed-off-by: Octavian Purdila <opurdila@ixiacom.com>
Applied, thanks.
prev parent reply other threads:[~2009-11-18 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 16:49 [net-next-2.6 PATCH] net: device name allocation cleanups Octavian Purdila
2009-11-17 17:01 ` Stephen Hemminger
2009-11-17 20:33 ` Octavian Purdila
2009-11-18 0:42 ` Stephen Hemminger
2009-11-18 0:46 ` Stephen Hemminger
2009-11-18 12:36 ` Octavian Purdila
2009-11-18 13:07 ` David 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=20091118.050749.39851073.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=shemminger@vyatta.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).