From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: akpm-3NddpPZAyC0@public.gmane.org
Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcollins-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org
Subject: Re: [patch 9/9] asus_acpi: Invert read of wled proc file to show correct state of LED
Date: Fri, 6 Jan 2006 15:28:54 +0100 [thread overview]
Message-ID: <20060106142853.GA20618@hell.org.pl> (raw)
In-Reply-To: <200601060631.k066VEgJ008147-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>
Thus wrote akpm-3NddpPZAyC0@public.gmane.org:
>
> From: Ben Collins <bcollins-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
>
> User with this equipment stated that writes to this file worked correctly,
> but that reads were showing inverted state (1 for off, 0 for on).
> Following the same style for reads, introduced an invert flag to read_led,
> and used it for wled.
Any background on this patch? I've never received such reports, so it must
be model-specific and require a model-specific work around.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-06 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 6:31 [patch 9/9] asus_acpi: Invert read of wled proc file to show correct state of LED akpm-3NddpPZAyC0
[not found] ` <200601060631.k066VEgJ008147-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>
2006-01-06 14:28 ` Karol Kozimor [this message]
[not found] ` <20060106142853.GA20618-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2006-01-06 15:19 ` Ben Collins
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=20060106142853.GA20618@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=bcollins-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.