All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Dan Williams <dcbw@redhat.com>, Bob Copeland <me@bobcopeland.com>,
	linux-wireless@vger.kernel.org, mabbaswireless@gmail.com
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Sat, 10 Jan 2009 10:27:59 +0100	[thread overview]
Message-ID: <1231579679.3685.10.camel@johannes> (raw)
In-Reply-To: <1ba2fa240901091553s387c1a95k3576ce6a82015434@mail.gmail.com> (sfid-20090110_005429_845681_92931D77)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Sat, 2009-01-10 at 01:53 +0200, Tomas Winkler wrote:

> I second this by stressing another issue. in the point that
> suspend/resume events shell be present to user space regardless of
> mac80211 specific talk with wpa_supplicant. Not only Wifi but also in
> my knowledge BT and other coms need user space application
> to close gracefully connection before kernel shuts in down.

But userspace is usually the one _invoking_ the suspend, so what I was
trying to say is that we don't care what userspace did right before
invoking suspend.

> Even sometime leavening shutting down interface managing application
> may reduce the crosstalk so that driver doesn't have go guess when
> application has finished it's shutdown. rtnl is probably not enough as
> there is still race who grabs it first.

No, the rtnl definitely is enough right now since userspace will do
whatever it needs to _before_ invoking the kernel suspend.

I say we should just put these patches in as they are.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-01-10  9:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15  3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22   ` Dan Williams
2008-12-15  9:28     ` Luis R. Rodriguez
2008-12-17 18:21     ` Bob Copeland
2008-12-23 20:30       ` Johannes Berg
2008-12-24  5:49         ` Bob Copeland
2008-12-24  7:16           ` Marcel Holtmann
2009-01-06 16:45             ` Dan Williams
2009-01-06 17:07               ` Bob Copeland
2009-01-06 17:14                 ` Johannes Berg
2009-01-06 17:35                   ` Bob Copeland
2009-01-06 17:43                     ` Johannes Berg
2009-01-06 18:01                       ` Bob Copeland
2009-01-06 18:16                         ` Johannes Berg
2009-01-06 17:12               ` Marcel Holtmann
2009-01-06 18:52                 ` Dan Williams
2009-01-06 19:36                   ` Marcel Holtmann
2009-01-06 20:05                     ` Johannes Berg
2009-01-09 23:53                       ` Tomas Winkler
2009-01-10  9:27                         ` Johannes Berg [this message]
2009-01-11 11:11                           ` Tomas Winkler
2009-01-11 14:40                             ` Bob Copeland
2009-01-08 16:39                     ` Dan Williams
2009-01-09  7:55                       ` Kalle Valo
2009-01-09 16:35                         ` Dan Williams
2009-01-09 16:44                           ` Kalle Valo

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=1231579679.3685.10.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mabbaswireless@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=me@bobcopeland.com \
    --cc=tomasw@gmail.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.