From: Johannes Berg <johannes@sipsolutions.net>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: How does rfkill work?
Date: Fri, 03 Apr 2009 21:22:53 +0200 [thread overview]
Message-ID: <1238786573.11352.0.camel@johannes.local> (raw)
In-Reply-To: <1238771745.5347.17.camel@dax.rpnet.com>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
On Fri, 2009-04-03 at 16:15 +0100, Richard Purdie wrote:
> > The trigger's name, should be
> > led_trigger.name = <something that is NULL> ? : dev_name(&some_dev)
> >
> > Does this make any sense to you?
>
> No, it doesn't make any sense and the 'fix' he posted isn't valid, just
> a workaround that happens to help. I suspect there is memory corruption
> going on somewhere...
That's what I suspected, thanks.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-03 19:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 4:59 How does rfkill work? Larry Finger
2009-04-02 9:56 ` Johannes Berg
2009-04-02 14:44 ` Larry Finger
2009-04-02 15:02 ` Johannes Berg
2009-04-02 15:22 ` Larry Finger
2009-04-02 15:55 ` Johannes Berg
2009-04-02 16:27 ` Johannes Berg
2009-04-02 18:18 ` Larry Finger
2009-04-02 18:28 ` Johannes Berg
2009-04-03 15:15 ` Richard Purdie
2009-04-03 19:22 ` Johannes Berg [this message]
2009-04-02 18:29 ` Johannes Berg
2009-04-02 18:42 ` Larry Finger
2009-04-02 18:48 ` Johannes Berg
2009-04-02 18:57 ` Johannes Berg
2009-04-02 20:36 ` Larry Finger
2009-04-02 20:50 ` Johannes Berg
2009-04-02 21:24 ` Larry Finger
2009-04-02 21:39 ` Johannes Berg
2009-04-02 21:59 ` Larry Finger
2009-04-02 22:09 ` Johannes Berg
2009-04-03 4:37 ` Marcel Holtmann
2009-04-03 4:57 ` Larry Finger
2009-04-03 5:09 ` Kay Sievers
2009-04-03 4:35 ` Marcel Holtmann
2009-04-03 9:01 ` Johannes Berg
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=1238786573.11352.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).