From: Paul Mundt <lethal@linux-sh.org>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-mips@linux-mips.org
Subject: Re: Advice on APM-EMU reunion
Date: Tue, 30 Jan 2007 10:00:55 +0900 [thread overview]
Message-ID: <20070130010055.GA15907@linux-sh.org> (raw)
In-Reply-To: <20070129230755.GA8705@enneenne.com>
On Tue, Jan 30, 2007 at 12:07:56AM +0100, Rodolfo Giometti wrote:
> some months ago I sent to the MIPS and ARM mail lists a patch to unify
> the several APM emulation codes adding a new dedicated directory so it
> can be used to put there the per board specific code avoiding code
> duplications (see files ./arch/arm/kernel/apm.c,
> ./arch/mips/kernel/apm.c and ./arch/sh/kernel/apm.c that are almost
> the same).
>
> The patch is here
> "http://www.linux-mips.org/archives/linux-mips/2006-07/msg00144.html"
> and it has been lost in the deep space...
>
Not quite, the rationale for it being dropped was here:
http://article.gmane.org/gmane.linux.kernel/485831
However, it has since been reposted:
http://article.gmane.org/gmane.linux.kernel/485833
http://article.gmane.org/gmane.linux.kernel/485834
http://article.gmane.org/gmane.linux.kernel/485835
http://article.gmane.org/gmane.linux.kernel/485837
and merged back in to -mm. This is all post 2.6.20 stuff, though..
next prev parent reply other threads:[~2007-01-30 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 23:07 Advice on APM-EMU reunion Rodolfo Giometti
2007-01-29 23:53 ` Richard Purdie
2007-01-29 23:59 ` Rodolfo Giometti
2007-01-30 1:00 ` Paul Mundt [this message]
2007-01-30 14:05 ` Ralf Baechle
2007-02-01 9:59 ` Advice on battery support [was: Advice on APM-EMU reunion] Rodolfo Giometti
2007-02-01 18:19 ` Matt Reimer
2007-02-02 21:27 ` [PATCH 1/1] APM-EMULATION: apm_get_power_status() should be NULL on init [was: Advice on battery support] Rodolfo Giometti
2007-02-02 21:35 ` Advice on battery support [was: Advice on APM-EMU reunion] Pavel Machek
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=20070130010055.GA15907@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=giometti@enneenne.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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.