From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH RESEND] MIPS: Alchemy: sleepcode without compile-time cputype dependencies
Date: Thu, 27 May 2010 16:06:30 +0100 [thread overview]
Message-ID: <20100527150630.GA4027@linux-mips.org> (raw)
In-Reply-To: <1274722972-19123-1-git-send-email-manuel.lauss@gmail.com>
On Mon, May 24, 2010 at 07:42:52PM +0200, Manuel Lauss wrote:
> Split the low-level sleepcode into per-cpu functions instead of
> relying on compile-time-defined cpu type.
>
> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> ---
> This patch didn't make it to 2.6.35 so I'm resending it.
Sorry, seems I or my patch-o-matic scripts somehow dropped
http://patchwork.linux-mips.org/patch/1038/ on the ground. That patch
was supposed to be applied. Anyway, I marked the old patch as superseeded
and I'm applying this one now.
Ralf
prev parent reply other threads:[~2010-05-27 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 17:42 [PATCH RESEND] MIPS: Alchemy: sleepcode without compile-time cputype dependencies Manuel Lauss
2010-05-27 15:06 ` Ralf Baechle [this message]
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=20100527150630.GA4027@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=manuel.lauss@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).