linux-kernel - Re: [PATCH v3 0/3] MAX8998 changes for RTC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Aug 2010 12:21:23 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Joonyoung Shim <dofmind@...il.com>
Cc:	Joonyoung Shim <jy0922.shim@...sung.com>,
	linux-kernel@...r.kernel.org, sameo@...ux.intel.com,
	broonie@...nsource.wolfsonmicro.com, lrg@...mlogic.co.uk,
	a.zummo@...ertech.it, p_gortmaker@...oo.com,
	kyungmin.park@...sung.com, m.szyprowski@...sung.com
Subject: Re: [PATCH v3 0/3] MAX8998 changes for RTC

On Wed, 25 Aug 2010 17:55:00 +0900
Joonyoung Shim <dofmind@...il.com> wrote:

> 2010/8/6 Joonyoung Shim <jy0922.shim@...sung.com>:
> > Hi.
> >
> > This patchset is to support the RTC provided by the Maxim 8998 chip. For
> > this first, needs i2c interface changes and interrupts support of
> > max8998 mfd driver.
> >
> > Changes since v1:
> >  - Fix missing braces of 3/3 patch from v1 review.
> >  - The rest is same with v1.
> >
> > Changes since v2:
> >  - add missing free_irq and rtc_valid_tm on rtc driver of 3/3 patch
> >  - The rest is same with v2.
> >
> > Joonyoung Shim (3):
> >      mfd: MAX8998: Use struct i2c_client to argument on i2c operation functions
> >      mfd: MAX8998: Add interrupts support
> >      rtc: Add MAX8998 rtc driver
> >
> 
> Ping. Is there any feedback?

They look good to me.  Things are pretty delayed at present as I (and
presumably others) recover from the -rc merge window..

I merged them.  Sam's acks on the MFD bits made life easier.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/