From: Andrew Morton <akpm@linux-foundation.org>
To: "Bahadir Balban" <bahadir.balban@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: 2.6.24-rc5 sysfs pci bridge duplicate symlink
Date: Fri, 28 Dec 2007 15:03:22 -0800 [thread overview]
Message-ID: <20071228150322.71e5ca49.akpm@linux-foundation.org> (raw)
In-Reply-To: <7ac1e90c0712280511y3a0f454cmc84e8c17f173c8dc@mail.gmail.com>
On Fri, 28 Dec 2007 13:11:37 +0000 "Bahadir Balban" <bahadir.balban@gmail.com> wrote:
> Hi,
>
> On ARM with PCI, I get this error since -rc2 (didn't try rc1):
>
> sysfs: duplicate filename 'bridge' can not be created
> WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> [<c00287fc>] (dump_stack+0x0/0x14) from [<c00cbc64>] (sysfs_add_one+0x50/0xf4)
> [<c00cbc14>] (sysfs_add_one+0x0/0xf4) from [<c00ccd30>]
> (sysfs_create_link+0xec/0x184)
> r6:cfca8b48 r5:cfca96c8 r4:cfc2fec0
> [<c00ccc44>] (sysfs_create_link+0x0/0x184) from [<c0160b44>]
> (pci_bus_add_devices+0xf0/0x144)
> r7:cfc5a2d4 r6:cfc5a2d4 r5:cfc5a2c0 r4:cfcad800
> [<c0160a54>] (pci_bus_add_devices+0x0/0x144) from [<c0160b30>]
> (pci_bus_add_devices+0xdc/0x144)
> r7:cfc5a3d4 r6:cfc5a3d4 r5:cfc5a3c0 r4:cfcadc00
> [<c0160a54>] (pci_bus_add_devices+0x0/0x144) from [<c0160b30>]
> (pci_bus_add_devices+0xdc/0x144)
> r7:cfc5a4d4 r6:cfc5a4d4 r5:cfc5a4c0 r4:cfc5d400
> [<c0160a54>] (pci_bus_add_devices+0x0/0x144) from [<c000a934>]
> (pci_common_init+0x148/0x184)
> r7:c035fd58 r6:cfc3e760 r5:c001e030 r4:cfc5a4c0
>
>
> Any idea why?
>
(suitable cc added)
next prev parent reply other threads:[~2007-12-28 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 13:11 Bahadir Balban
2007-12-28 23:03 ` Andrew Morton [this message]
2007-12-28 23:50 ` Russell King - ARM Linux
2008-01-10 3:55 ` Greg KH
2008-01-16 19:02 ` Bahadir Balban
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=20071228150322.71e5ca49.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bahadir.balban@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome