From: Holger Schurig <h.schurig@mn-logistik.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] "/sys/devices/legacy" is an offending term
Date: Thu, 23 Oct 2003 12:50:42 +0200 [thread overview]
Message-ID: <bn8bq2$588$1@sea.gmane.org> (raw)
> echo 50 > /sys/devices/legacy/sa1100fb/brightness
Is there any change to get rid of this "legacy"? From my (still quite
limited) understanding of the english language, this means old/outdated
and has a not-so-good connotation. It's not just a fact, but puts a
negative value into something. But maybe I'm wrong.
Anyway, on embedded arches it makes no sense to say "Oh, PCI is all wow,
non-pci is all boo".
I talked on the arm-linux-kernel mailing list and Russell King answered:
> I brought this exact point up with Pat Mochel at OLS this year. At
> the time, he agreed that it should be renamed to "platform".
>
> I don't know if such a change will now be allowed for the 2.6 series,
> since it'll effectively be a user-visible interface change.
>
> I do know that Pat is heavily overloaded with work, which probably
> explains why it hasn't happened.
In the hope that this happens I included a patch below.
If wished, I can provide a bigger patch that renames "
legacy_bus" to "legacy_bus" as well.
#
# Patch managed by http://www.mn-logistik.de/unsupported/pxa250/patcher
#
--- linux-2.6/drivers/base/platform.c~legacy-platform
+++ linux-2.6/drivers/base/platform.c
@@ -15,7 +15,7 @@
#include <linux/init.h>
struct device legacy_bus = {
- .bus_id = "legacy",
+ .bus_id = "platform",
};
/**
--
Try Linux 2.6 from BitKeeper for PXA2x0 CPUs at
http://www.mn-logistik.de/unsupported/linux-2.6/
reply other threads:[~2003-10-23 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='bn8bq2$588$1@sea.gmane.org' \
--to=h.schurig@mn-logistik.de \
--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