On Wed, Feb 11, 2015 at 10:21:38AM +0100, Paul Bolle wrote:
TL;DR: what exactly should I resend and when?
This is disappointing; you're someone who's been contributing for quite some time now, I'd really expect you to be faimilar with the process of submitting patches and able to identify answers to your questions.
What's posted doesn't apply against -next.
That's because of trivial conflicts with commit a59aa180ea56 ("ASoC: samsung: Replace depends on REGMAP_I2C with depends on I2C"). That commit landed in next-20150127 (ie, eight days after I sent this short series). I guess I resolved these conflicts in the local version of these patches and promptly forgot about them, as they were so trivial.
For something like this I'm just not even going to look at what's required to fix up by hand, sorry.
As ever submit against the tree listed in MAINTAINERS
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Which is not entirely obvious, since this series only touches files below sound/soc/samsung/. That directory is mentioned in MAINTAINERS under "ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" and under "SAMSUNG AUDIO (ASoC) DRIVERS". (Why does that directory need two entries?) Neither entry mention a repository.
Of course neither of those entries list me either yet you managed to figure out that you should send the patch to me. The same process that helps you identify that things should be submitted to the subsystem maintainers should allow you to identify where they're likely to try to apply changes. Or simply looking at how other similar patches get merged.
And now I wonder what I should resend: the three patches 2/4, 3/4, and 4/4 with the trivial conflicts resolved or the entire series? And when do you prefer I resend?
Again this is something I'd really expect you to be familiar with. As ever if there are changes you would like to see integrated into the kernel then please submit them using the normal patch submission process.