Prev: tracing: Consolidate protection of reader access to the ring buffer
Next: Linux IO scalability and pushing over million IOPS over software iSCSI?
From: Dale Farnsworth on 22 Jun 2010 09:40
On Tue, Jun 22, 2010 at 05:09:03PM +0800, Wan ZongShun wrote:
> Use rtc_valid_tm to check returning tm for max6900,
> it can avoid returning wrong tm value.
> ---
> drivers/rtc/rtc-max6900.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/rtc/rtc-max6900.c b/drivers/rtc/rtc-max6900.c
> index a4f6665..486142c 100644
> --- a/drivers/rtc/rtc-max6900.c
> +++ b/drivers/rtc/rtc-max6900.c
> @@ -159,7 +159,7 @@ static int max6900_i2c_read_time(struct i2c_client *client, struct rtc_time *tm)
> bcd2bin(regs[MAX6900_REG_CENTURY]) * 100 - 1900;
> tm->tm_wday = bcd2bin(regs[MAX6900_REG_DW]);
>
> - return 0;
> + return rtc_valid_tm(tm);
> }
>
> static int max6900_i2c_clear_write_protect(struct i2c_client *client)

Ack.

Thanks,
-Dale
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: tracing: Consolidate protection of reader access to the ring buffer
Next: Linux IO scalability and pushing over million IOPS over software iSCSI?