From: Florian Mickler <florian@mickler.org>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@lists.osdl.org, linux-input@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/8] Suspend block api (version 6)
Date: Thu, 27 May 2010 10:04:53 +0200 [thread overview]
Message-ID: <20100527100453.1d55c87e@schatten.dmk.lab> (raw)
In-Reply-To: <CEE6BB42CAD6E947908279175AF8470A025A8206ED@EXDCVYMBSTM006.EQ1STM.local>
On Thu, 27 May 2010 09:46:51 +0200
Linus WALLEIJ <linus.walleij@stericsson.com> wrote:
> If yes then OK, it's not totally elegant but if that is
> where we have to go, I can live with it. There will likely
> be people who implement for only one or the other semantic
> behaviour, but we have worse things to cope with already.
Alan Cox suggested, that this kind of explicit requirement definition
might be necessary for all drivers anyway in the long run.
That way, the semantic differences between those two cases would
vanish.
Cheers,
Flo
next prev parent reply other threads:[~2010-05-27 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1272667021-21312-1-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-2-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-3-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-4-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-5-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-6-git-send-email-arve@android.com>
[not found] ` <1272667021-21312-7-git-send-email-arve@android.com>
2010-04-30 22:37 ` [PATCH 7/8] Input: Block suspend while event queue is not empty Arve Hjønnevåg
[not found] ` <87wrvl5479.fsf@deeprootsystems.com>
[not found] ` <20100503180741.GB2098@rakim.wolfsonmicro.main>
[not found] ` <201005032318.35383.rjw@sisk.pl>
[not found] ` <87sk68r1zh.fsf@deeprootsystems.com>
[not found] ` <s2qd6200be21005031709r28420f0ezf3cf286517ee9114@mail.gmail.com>
2010-05-14 20:27 ` [PATCH 0/8] Suspend block api (version 6) Paul Walmsley
2010-05-14 22:18 ` Arve Hjønnevåg
2010-05-15 2:25 ` Alan Stern
2010-05-15 4:02 ` Arve Hjønnevåg
2010-05-15 21:25 ` Alan Stern
2010-05-17 4:54 ` Arve Hjønnevåg
2010-05-18 2:26 ` Paul Walmsley
2010-05-18 3:21 ` Arve Hjønnevåg
2010-05-18 7:03 ` Henrik Rydberg
2010-05-18 19:39 ` Rafael J. Wysocki
2010-05-25 9:41 ` Paul Walmsley
2010-05-25 23:08 ` Arve Hjønnevåg
2010-05-26 7:23 ` Linus WALLEIJ
2010-05-26 16:01 ` Alan Stern
2010-05-27 7:46 ` Linus WALLEIJ
2010-05-27 8:04 ` Florian Mickler [this message]
2010-05-27 8:40 ` Arve Hjønnevåg
2010-05-27 15:33 ` Alan Stern
2010-05-28 11:54 ` Linus WALLEIJ
2010-05-20 23:37 ` David Brownell
2010-05-25 16:51 ` Dmitry Torokhov
2010-05-25 18:25 ` Alan Stern
2010-05-25 18:33 ` Dmitry Torokhov
2010-05-25 22:05 ` Arve Hjønnevåg
2010-05-25 22:28 ` Dmitry Torokhov
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=20100527100453.1d55c87e@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.osdl.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).