linux-kernel - Re: [PATCH 29/29] drivers/regulator: Update WARN uses

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]

Message-ID: <alpine.LNX.2.00.1012071549150.14806@pobox.suse.cz>
Date:	Tue, 7 Dec 2010 15:50:32 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org,
	lrg@...mlogic.co.uk
Subject: Re: [PATCH 29/29] drivers/regulator: Update WARN uses

On Tue, 7 Dec 2010, Mark Brown wrote:

> On Mon, Dec 06, 2010 at 02:05:19PM -0800, Joe Perches wrote:
> > Align arguments.
> > 
> > Signed-off-by: Joe Perches <joe@...ches.com>
> 
> Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> 
> but please do remember to send patches to maintainers - trying to merge
> patches without going through the maintainers means that people working
> on the actual tree concerned may either replicate your work or introduce
> conflicts with your patches, neither of which is good.

That happened here:

	https://lkml.org/lkml/2010/11/1/107

but the patch is not in linux-next after more than one month. Which is why 
Joe is resending it for inclusion through my queue.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/