From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Andrew Morton <akpm@osdl.org>,
Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4-mm2
Date: Thu, 19 May 2005 16:59:10 +0200 [thread overview]
Message-ID: <428CA9BE.8010107@ens-lyon.org> (raw)
In-Reply-To: <20050516021302.13bd285a.akpm@osdl.org>
Andrew Morton a écrit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
>
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
>
> echo subscribe mm-commits | mail majordomo@vger.kernel.org
>
> - x86_64 architecture update from Andi.
>
> - Everything up to and including `spurious-interrupt-fix.patch' is planned
> for 2.6.12 merging. Plus a few other things in there.
>
> - Another DVB subsystem update
Hi Andrew and Dominik,
Since mm2, udev cannot rename my pcmcia wireless interface.
rc4 and rc4-mm1 successfully rename it from eth0 to wifi.
rc4-mm2 only renames the internal interface, not the pcmcia wifi one.
When I insert the card, This line appears in syslog:
udev[9500]: configured rule in '/etc/udev/rules.d/brice.rules[4]'
applied, 'eth0' becomes 'wifi'
But the interface is still called eth0.
Any idea ?
Thanks,
Brice
PS: Richard Purdie's patch (http://lkml.org/lkml/2005/5/18/303) fixed my
previous cardctl breakage, but it doesn't change anything regarding this
bug.
next prev parent reply other threads:[~2005-05-19 15:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 9:13 2.6.12-rc4-mm2 Andrew Morton
2005-05-16 9:25 ` 2.6.12-rc4-mm2 Russell King
2005-05-16 10:50 ` 2.6.12-rc4-mm2 Danny ter Haar
2005-05-16 11:17 ` 2.6.12-rc4-mm2 Alexey Dobriyan
2005-05-16 11:38 ` 2.6.12-rc4-mm2 Danny ter Haar
2005-05-16 12:15 ` 2.6.12-rc4-mm2 Alexey Dobriyan
2005-05-16 17:11 ` 2.6.12-rc4-mm2 Danny ter Haar
2005-05-16 17:43 ` 2.6.12-rc4-mm2 Alexey Dobriyan
2005-05-16 19:30 ` 2.6.12-rc4-mm2 Danny ter Haar
2005-05-16 12:30 ` 2.6.12-rc4-mm2 Brice Goglin
2005-05-16 17:46 ` 2.6.12-rc4-mm2, alpha and mips broke Jan Dittmer
2005-05-16 20:09 ` Andrew Morton
2005-05-16 19:18 ` 2.6.12-rc4-mm2: proc-pid-smaps.patch broke nommu Adrian Bunk
2005-05-21 2:19 ` Mauricio Lin
2005-05-21 2:39 ` Mauricio Lin
2005-07-21 15:04 ` Adrian Bunk
2005-05-17 9:06 ` 2.6.12-rc4-mm2 Brice Goglin
2005-05-17 16:38 ` 2.6.12-rc4-mm2 Richard Purdie
2005-05-18 22:45 ` 2.6.12-rc4-mm2 Richard Purdie
2005-05-18 7:14 ` 2.6.12-rc4-mm2 Coywolf Qi Hunt
2005-05-18 20:26 ` 2.6.12-rc4-mm2 Alexander Nyberg
2005-05-19 14:59 ` Brice Goglin [this message]
2005-05-22 21:27 ` [bugfix] try_to_unmap_cluster() passes out-of-bounds pte to pte_unmap() William Lee Irwin III
2005-05-22 22:00 ` Andrew Morton
2005-05-24 0:14 ` Andrew Morton
2005-05-24 2:48 ` William Lee Irwin III
2005-05-24 4:38 ` Hugh Dickins
2005-05-24 8:02 ` Nick Piggin
2007-06-27 0:35 ` Problems with fb console [was Re: 2.6.12-rc4-mm2] J.A. Magallón
2007-06-27 0:54 ` Andrew Morton
2007-06-27 14:21 ` H. Peter Anvin
2007-06-27 7:20 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 10:31 2.6.12-rc4-mm1 Andrew Morton
2005-05-14 11:27 ` 2.6.12-rc4-mm1 Richard Purdie
2005-05-16 11:27 ` 2.6.12-rc4-mm2 Richard Purdie
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=428CA9BE.8010107@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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