Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Linux MIPS List <linux-mips@linux-mips.org>, rtc-linux@googlegroups.com
Subject: Re: [PATCH 1/2]: Add support for Dallas/Maxim DS1685/1687 RTC
Date: Fri, 18 Feb 2011 06:02:00 -0500	[thread overview]
Message-ID: <4D5E51A8.8070408@gentoo.org> (raw)
In-Reply-To: <4D5D09FF.6010005@metafoo.de>

On 02/17/2011 06:43, Lars-Peter Clausen wrote:
>
> That is what I meant. Pass the return value of rtc_valid_tm on, instead of
> setting the time to 0 and pretend everything went fine.
> You can still keep the dev_err though, no problem with that.

Okay, I got confused by this and thought you were referring to the quoted test 
box below in your first response.  My bad.  You're referring to the tail end of 
ds1685_rtc_read_time.

To clarify, this construct exists in four existing RTC drivers.  If this is 
wrong, I suggest fixing these four drivers, lest someone else come along and try 
to copy the idea, thinking it's the RightThing();

	drivers/rtc/rtc-ds1553.c:131
	drivers/rtc/rtc-ds1742.c:119
	drivers/rtc/rtc-rs5c348.c:136
	drivers/rtc/rtc-stk17ta8.c:133

I am going to assume the proper approach is:
	return rtc_Valid_tm(tm);


Cheers!,

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org

"The past tempts us, the present confuses us, the future frightens us.  And our 
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

      parent reply	other threads:[~2011-02-18 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 11:39 [PATCH 1/2]: Add support for Dallas/Maxim DS1685/1687 RTC Kumba
2011-02-16 23:23 ` Lars-Peter Clausen
2011-02-17  5:45   ` Kumba
2011-02-17  7:31     ` Manuel Lauss
2011-02-17  8:17       ` Kumba
2011-02-17  8:39         ` Manuel Lauss
2011-02-17  9:57   ` Kumba
2011-02-17 11:43     ` Lars-Peter Clausen
2011-02-17 18:47       ` Kumba
2011-02-18 11:02       ` Kumba [this message]

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=4D5E51A8.8070408@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=lars@metafoo.de \
    --cc=linux-mips@linux-mips.org \
    --cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox