linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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] MIPS: Alchemy: sleepcode without compile-time cputype dependencies
Date: Wed, 10 Mar 2010 17:04:42 +0100	[thread overview]
Message-ID: <20100310160442.GA15118@linux-mips.org> (raw)
In-Reply-To: <1268076181-29642-1-git-send-email-manuel.lauss@gmail.com>

On Mon, Mar 08, 2010 at 08:22:59PM +0100, Manuel Lauss wrote:

> Split the low-level sleepcode into per-memory-controller-generation
> functions and figure out which one to call at runtime instead of
> relying on compile-time-defined cpu types.
> 
> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>

Thanks, queued for 2.6.35.

  Ralf

      parent reply	other threads:[~2010-03-10 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 19:22 [PATCH] MIPS: Alchemy: sleepcode without compile-time cputype dependencies Manuel Lauss
2010-03-08 19:23 ` [RFC PATCH] MIPS: Alchemy: add sysdev for both irq controllers Manuel Lauss
2010-03-10 16:13   ` Ralf Baechle
2010-03-10 19:03     ` Manuel Lauss
2010-03-08 19:23 ` [PATCH] MIPS: Alchemy: move MMC driver registration to board code Manuel Lauss
2010-03-09 11:33   ` Sergei Shtylyov
2010-03-09 11:45     ` Manuel Lauss
2010-03-09 11:45       ` Manuel Lauss
2010-03-09 11:51       ` Sergei Shtylyov
2010-03-09 12:03         ` Manuel Lauss
2010-03-09 12:03           ` Manuel Lauss
2010-03-10 16:48           ` Ralf Baechle
2010-03-10 18:34             ` Manuel Lauss
2010-03-10 18:34               ` Manuel Lauss
2010-03-10 16:04 ` 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=20100310160442.GA15118@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).