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

[Lee Jones]

> > > The advice here is usually that sending against -next is a good proxy
> > > for sending against the individual tree without having to figure out all
> > > the different trees - almost all of the time the effect is the same.
> > > This only applies when sending patches via e-mail, for git pulls it's an
> > > absolute no of course.
> 
> > Good point. But it's worth reiterating that this should only be done
> > if you have dependencies which haven't yet reached Mainline. 
> 
> 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.

-- 
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/