From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Alessandro Zummo <a.zummo@towertech.it>,
David Brownell <dbrownell@users.sourceforge.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: rtc_valid_tm doesn't check tm_wday
Date: Tue, 29 Apr 2008 08:44:08 +0200 [thread overview]
Message-ID: <20080429064408.GA8352@digi.com> (raw)
Hello,
I'm currently writing an rtc driver and want to use rtc_valid_tm to
assert to have a valid date before writing it to the rtc.
Now I wonder why rtc_valid_tm doesn't check tm_wday for being in the
range [0 .. 6]. Is there a reason? I could imagine that you want to
be able to check paritial "struct rtc_time"s, too.
So should I check tm_wday myself?
Best regards
Uwe
--
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
next reply other threads:[~2008-04-29 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 6:44 Uwe Kleine-König [this message]
2008-04-29 10:40 ` rtc_valid_tm doesn't check tm_wday David Brownell
2008-04-29 12:22 ` Uwe Kleine-König
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=20080429064408.GA8352@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=a.zummo@towertech.it \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.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