public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Manuel Lauss <manuel.lauss@googlemail.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-pcmcia@lists.infradead.org,
	Manuel Lauss <manuel.lauss@gmail.com>,
	linux-pm@l
Subject: Re: [PATCH v2] pcmcia: db1xxx-ss: suspend/resume fix
Date: Tue, 23 Mar 2010 18:15:36 +0100	[thread overview]
Message-ID: <f861ec6f1003231015j73d6de9dp7a3a4e087aabda0a@mail.gmail.com> (raw)
In-Reply-To: <20100322205814.GB15250@isilmar.linta.de>

Howdy,

On Mon, Mar 22, 2010 at 9:58 PM, Dominik Brodowski
<linux@dominikbrodowski.net> wrote:
> Hm, what about using two commits currently in my tree for 2.6.36 instead,
> which should fix all socket drivers?
>
>    power: support _noirq actions on device types and classes
>    pcmcia: use dev_pm_ops for class pcmcia_socket_class
>
> Manuel: Could you try whether they also solve these issues? If so, I'd

Yes it does, works on my MIPS test systems.


> propose pushing both patches already for 2.6.36. Rafael: do you concur?

I hope you meant 2.6.34


Thanks!
     Manuel Lauss

  reply	other threads:[~2010-03-23 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1269287003-15523-1-git-send-email-manuel.lauss@gmail.com>
2010-03-22 20:58 ` [PATCH v2] pcmcia: db1xxx-ss: suspend/resume fix Dominik Brodowski
2010-03-23 17:15   ` Manuel Lauss [this message]
2010-03-23 22:02     ` Rafael J. Wysocki
2010-03-24 17:04       ` Manuel Lauss
     [not found]       ` <f861ec6f1003241004r629f0b35webd9d1925fe5f0d9@mail.gmail.com>
2010-03-24 19:18         ` Dominik Brodowski
     [not found]         ` <20100324191844.GA22767@isilmar.linta.de>
2010-03-24 19:23           ` Manuel Lauss
     [not found]           ` <f861ec6f1003241223v11e3eaf3sf4e2c0a7594a38df@mail.gmail.com>
2010-03-24 20:03             ` Rafael J. Wysocki

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=f861ec6f1003231015j73d6de9dp7a3a4e087aabda0a@mail.gmail.com \
    --to=manuel.lauss@googlemail.com \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux-pm@l \
    --cc=manuel.lauss@gmail.com \
    --cc=rjw@sisk.pl \
    /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