Linux MIPS Architecture development
 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>
Subject: Re: [PATCH V2] MIPS: Alchemy: redo PCI as platform driver
Date: Fri, 7 Oct 2011 17:33:30 +0100	[thread overview]
Message-ID: <20111007163330.GA26918@linux-mips.org> (raw)
In-Reply-To: <1317908261-25608-1-git-send-email-manuel.lauss@googlemail.com>

On Thu, Oct 06, 2011 at 03:37:41PM +0200, Manuel Lauss wrote:

> V2: changed PM to use syscore_ops instead of the platform_driver PM callbacks.
>     syscore_ops are called much earlier during the resume process which
>     makes restoring the wired entry much more straightforward.

Shouldn't the handling of wired entries rather be done in
arch/mips/power/cpu.c?

  Ralf

  reply	other threads:[~2011-10-07 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 13:37 [PATCH V2] MIPS: Alchemy: redo PCI as platform driver Manuel Lauss
2011-10-07 16:33 ` Ralf Baechle [this message]
2011-10-07 17:33   ` Manuel Lauss

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=20111007163330.GA26918@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --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