From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Jean Delvare <khali@linux-fr.org>,
i2c@lm-sensors.org, Ben Dooks <ben-linux@fluff.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] i2c: MPC8349E-mITX Power Management and GPIO expander driver
Date: Fri, 10 Oct 2008 19:16:25 +0400 [thread overview]
Message-ID: <20081010151625.GA7462@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <CB31A54E-7518-4E26-8A5C-AC3CBB0F1384@kernel.crashing.org>
On Fri, Oct 10, 2008 at 09:58:44AM -0500, Kumar Gala wrote:
[...]
>>> is the plan to connect ppc_md.machine_shutdown() with this?
>>
>> You mean poweroff? It's already connected.
>>
>> + /* XXX: this is potentially racy, but there is no lock for
>> ppc_md */
>> + if (!ppc_md.power_off) {
>> + glob_mcu = mcu;
>> + ppc_md.power_off = mcu_power_off;
>> + dev_info(&client->dev, "will provide power-off
>> service\n");
>> + }
>
>
> uuh, yeah.. poweroff :)
>
> and look at that. Is this in Jean's queue?
Nope. Here's what Jean wrote:
On Wed, Oct 01, 2008 at 01:22:48PM +0200, Jean Delvare wrote:
> I do not have the time to review these patches (and, honestly, have no
> interest in them.) So I will not merge them but I have no objection to
> them being merged by somebody else.
So.. I think it could easily go through the powerpc tree.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2008-10-10 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 14:13 [PATCH 2/2] i2c: MPC8349E-mITX Power Management and GPIO expander driver Anton Vorontsov
2008-10-10 14:22 ` Kumar Gala
2008-10-10 14:45 ` Anton Vorontsov
2008-10-10 14:58 ` Kumar Gala
2008-10-10 15:16 ` Anton Vorontsov [this message]
2008-10-10 18:46 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2008-09-19 18:03 Anton Vorontsov
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=20081010151625.GA7462@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=ben-linux@fluff.org \
--cc=galak@kernel.crashing.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linuxppc-dev@ozlabs.org \
/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).