From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Manuel Lauss <mano@roarinelk.homelinux.net>,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [RFC PATCH] MIPS: Alchemy: add sysdev for both irq controllers
Date: Wed, 10 Mar 2010 17:13:12 +0100 [thread overview]
Message-ID: <20100310161312.GB15118@linux-mips.org> (raw)
In-Reply-To: <1268076181-29642-2-git-send-email-manuel.lauss@gmail.com>
On Mon, Mar 08, 2010 at 08:23:00PM +0100, Manuel Lauss wrote:
> From: Manuel Lauss <mano@roarinelk.homelinux.net>
>
> Use a sysdev to implement PM methods for the Au1000 interrupt controllers.
>
> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> ---
> Works on DB1200, not sure though whether this is the correct approach.
> Applies cleanly only on top of "sleepcode-without-compile-time-cputype"
> patch.
At a quick glance this looks good but since you marked your patch as RFC
I'll do the same in patchwork (http://patchwork.linux-mips.org/patch/1039/)
until you ask me to queue it or resubmit.
Thanks,
Ralf
next prev parent reply other threads:[~2010-03-10 16:13 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 [this message]
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 ` [PATCH] MIPS: Alchemy: sleepcode without compile-time cputype dependencies Ralf Baechle
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=20100310161312.GB15118@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
--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 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.