linux-kernel - Re: [PATCH 02/35 linux-next] regulator: constify of_device

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:	Thu, 19 Mar 2015 17:44:04 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Fabian Frederick <fabf@...net.be>
Cc:	Tony Lindgren <tony@...mide.com>, Joe Perches <joe@...ches.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
	linux-omap@...r.kernel.org
Subject: Re: [PATCH 02/35 linux-next] regulator: constify of_device_id array

On Tue, Mar 17, 2015 at 06:26:17PM +0100, Fabian Frederick wrote:
> > On 17 March 2015 at 18:19 Mark Brown <broonie@...nel.org> wrote:

> > Well, another thing to do if there's no dependencies is to just send
> > each patch separately - there's no real relationship between the
> > patches.  This also avoids the issue.

> Such trivial updates are generally applied by David or Greg
> after receiving some ack. That's the reason for the patchset :)

It's pretty disappointing if that's the case, though it might be
something connected with the submission style - for most of the kernel
patches would normally be handled directly by the maintainer.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)