From: Dmitry Torokhov <dtor_core@ameritech.net>
To: All Linux <allinux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.12-rc1, ./drivers/base/platform.c
Date: Tue, 22 Mar 2005 01:04:33 -0500 [thread overview]
Message-ID: <200503220104.34123.dtor_core@ameritech.net> (raw)
In-Reply-To: <cb57165a050321213210961749@mail.gmail.com>
On Tuesday 22 March 2005 00:32, All Linux wrote:
> The latest prepatch, 2.6.12-rc1, introduced the following change.
>
> --- a/drivers/base/platform.c 2005-03-17 17:35:04 -08:00
> +++ b/drivers/base/platform.c 2005-03-17 17:35:04 -08:00
> @@ -131,7 +131,7 @@
> pdev->dev.bus = &platform_bus_type;
>
> if (pdev->id != -1)
> - snprintf(pdev->dev.bus_id, BUS_ID_SIZE, "%s%u",
> pdev->name, pdev->id);
> + snprintf(pdev->dev.bus_id, BUS_ID_SIZE, "%s.%u",
> pdev->name, pdev->id);
> else
> strlcpy(pdev->dev.bus_id, pdev->name, BUS_ID_SIZE);
>
> It causes problem, as most platform files, for example,
> arch/ppc/platforms/katana.c, still use the old name without ".". I do
> not understand why bus_id "mpsc.0" is better than "mpsc0".
> Please explain what is the benefit of introducing such a change,
> before I can submit a patch for all those platform files to work with
> this change.
> Please CC me, as I am currently not in the list.
>
Devices/drivers ending with a digit, such as i8250, produce "wierd"
names - i82500, i82501, etc.
--
Dmitry
next prev parent reply other threads:[~2005-03-22 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 5:32 [PATCH] 2.6.12-rc1, ./drivers/base/platform.c All Linux
2005-03-22 6:04 ` Dmitry Torokhov [this message]
2005-03-22 18:32 ` Brian Waite
2005-03-22 20:22 ` All Linux
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=200503220104.34123.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=allinux@gmail.com \
--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 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.