From: Ingo Molnar <mingo@elte.hu>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [bug, 2.6.24-rc1] sysfs: duplicate filename 'eth0' can not be created
Date: Mon, 29 Oct 2007 22:48:50 +0100 [thread overview]
Message-ID: <20071029214850.GA31152@elte.hu> (raw)
In-Reply-To: <20071029144016.06c03b7c@freepuppy.rosehill>
* Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> Already fixed post 2.6.24-rc1
>
> commit c8d90dca3211966ba5189e0f3d4bccd558d9ae08
> Author: Stephen Hemminger <shemminger@linux-foundation.org>
> Date: Fri Oct 26 03:53:42 2007 -0700
>
> [NET] dev_change_name: ignore changes to same name
ah, nice - that explains it. I just booted with very latest -git and the
warning is gone.
Ingo
next prev parent reply other threads:[~2007-10-29 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:17 [bug, 2.6.24-rc1] sysfs: duplicate filename 'eth0' can not be created Ingo Molnar
2007-10-29 21:35 ` Jeff Garzik
2007-10-29 21:49 ` Rick Jones
2007-10-29 21:40 ` Stephen Hemminger
2007-10-29 21:48 ` Ingo Molnar [this message]
2007-10-29 22:36 ` David Miller
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=20071029214850.GA31152@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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.