linux-kernel - Re: [PATCH v3 02/15] mfd: max14577: Rename and add MAX14577 symbols to prepare for max77836

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] [day] [month] [year] [list]

Message-id: <1392886487.3648.12.camel@AMDC1943>
Date:	Thu, 20 Feb 2014 09:54:47 +0100
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Anton Vorontsov <anton@...msg.org>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Chanwoo Choi <cw00.choi@...sung.com>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Tomasz Figa <t.figa@...sung.com>
Subject: Re: [PATCH v3 02/15] mfd: max14577: Rename and add MAX14577 symbols to
 prepare for max77836

On Wed, 2014-02-19 at 23:11 +0900, Mark Brown wrote:
> On Wed, Feb 19, 2014 at 01:44:41PM +0100, Krzysztof Kozlowski wrote:
> 
> > I want to push whole MAX77836 patchset through Lee Jones' MFD tree and I
> > still need acks from power and regulator subsystems.
> 
> > I would appreciate if you could find time to look at these patches and
> > let me know your opinion (or just add Acked-by):
> > [PATCH v3 02/15] mfd: max14577: Rename and add MAX14577 symbols...
> > [PATCH v3 03/15] mfd: max14577: Rename state container to maxim_core
> > [PATCH v3 04/15] mfd: max14577: Add "muic" suffix to regmap and irq_chip
> 
> I don't have these patches, I expect it looked like the series was going
> to get a respin.

Hmmm, I'll send the next version of this patchset.

> 
> To be honest the number of large patch serieses you've been sending
> iterations of (sometimes partial series without context too) doesn't
> push them up the priority list, it'd help to rate limit things a bit.

I understand, especially that such drivers touch multiple subsystems.

Best regards,
Krzysztof


--
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/