From: Brian Waite <waite@skycomputers.com>
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 13:32:09 -0500 [thread overview]
Message-ID: <200503221332.15068.waite@skycomputers.com> (raw)
In-Reply-To: <cb57165a050321213210961749@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Tuesday 22 March 2005 00:32, All Linux wrote:
> It causes problem, as most platform files, for example,
> arch/ppc/platforms/katana.c, still use the old name without ".". I do
Mark Greer recently produced a patch for the katana board among other PPC platforms
to fix this breakage. I'll look for the announcement mail but I recall seeing it a day or two ago.
Thanks
Brian
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-22 18:45 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
2005-03-22 18:32 ` Brian Waite [this message]
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=200503221332.15068.waite@skycomputers.com \
--to=waite@skycomputers.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox