linux-kernel - Re: [PATCH V1 2/3] MFD: da9052: Add new DA9053 BC chip variant

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: <20140226115917.GL9195@lee--X1>
Date:	Wed, 26 Feb 2014 11:59:17 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	"Opensource [Anthony Olech]" <anthony.olech.opensource@...semi.com>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Dajun Chen <david.chen@...semi.com>
Subject: Re: [PATCH V1 2/3] MFD: da9052: Add new DA9053 BC chip variant

> > > It can be worth doing anyway with a subsystem that's actively developed
> > > since sometimees the dependencies are the other way - the APIs in Linus'
> > > tree may have gone away.
> 
> > Then what happens if the tree that your patch finally gets sucked into
> > is pulled before the one you've written your code against? I'd say
> > basing your code on -next is generally a bad idea.
> 
> Submitters should defintely at the very least be checking against the
> subsystem tree (since that's what they're really submitting against) -
> it's always annoying when someone submits code that either doesn't
> apply or fails to build with the current tree.

+1

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/