From: Pavel Machek <pavel@ucw.cz>
To: Shaohua Li <shaohua.li@intel.com>
Cc: ronald.mythtv@gmail.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: /proc/acpi/alarm -- does it work or not?
Date: Sun, 15 Jan 2006 15:13:45 +0000 [thread overview]
Message-ID: <20060115151345.GA2694@ucw.cz> (raw)
In-Reply-To: <1136863261.5750.4.camel@sli10-desk.sh.intel.com>
Hi!
> > pavel@amd:/data/l/linux$
> >
> > ...but /proc/acpi/alarm still behaves very strangely:
> >
> > 2006-01-00 12:42:00
> > root@amd:/proc/acpi# echo '2006-01-01 12:34:56' > alarm
> > root@amd:/proc/acpi# cat alarm
> > 2006-01-01 12:34:56
> > root@amd:/proc/acpi# echo '2006-09-01 12:34:56' > alarm
> > root@amd:/proc/acpi# cat alarm
> > 2006-01-01 12:34:56
> > root@amd:/proc/acpi# echo '2006-01-09 12:34:56' > alarm
> > root@amd:/proc/acpi# cat alarm
> > 2006-01-09 12:34:56
> > root@amd:/proc/acpi# echo '2006-02-09 12:34:56' > alarm
> > root@amd:/proc/acpi# cat alarm
> > 2006-01-09 12:34:56
> > root@amd:/proc/acpi#
> >
> > ...why does it hate february and september?
> No. Setting day, month, century for alarm is optional. This means your
> system doesn't support setting month and century. But maybe we should
> print some infos here ...
Yes, more info would be nice. What is "correct" way to test
if systen supports day/month/year/century in alarm?
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-18 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59D45D057E9702469E5775CBB56411F1013CF084@pdsmsx406>
2006-01-09 15:44 ` /proc/acpi/alarm -- does it work or not? Pavel Machek
2006-01-10 3:20 ` Shaohua Li
2006-01-15 15:13 ` Pavel Machek [this message]
2005-12-26 20:43 Pavel Machek
[not found] ` <20051226204305.GA2028-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-12-28 18:24 ` Karol Kozimor
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=20060115151345.GA2694@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ronald.mythtv@gmail.com \
--cc=shaohua.li@intel.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.