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: <1291736651.3275.88.camel@odin>
Date:	Tue, 07 Dec 2010 15:44:11 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 29/29] drivers/regulator: Update WARN uses

On Tue, 2010-12-07 at 16:31 +0100, Jiri Kosina wrote:
> On Tue, 7 Dec 2010, Mark Brown 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.
> > 
> > That's not a reason to drop people from the CCs when reposting, and when
> > reposting it's always good to include any reviews you got previously.
> 
> Yes, collecting of the previously collected Acked-by: would definitely be 
> good. Joe, could you please include it next time?
> 
> > Indeed, looking at the original posting you'll see he sent it directly
> > to you first time around as well as CCing the maintainers.
> 
> Yes, but I am not merging these large series which span gazillion of 
> subsystems at first. I only tend to act as a fallback for those parts of 
> the series which were not merged by maintainers.
> 
Sorry, this is my fault. I've been very busy lately and this one slipped
through. I can take it now if you want ?

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ