On Thu, Dec 22, 2011 at 08:38:39PM +0800, Shawn Guo wrote:

On 22 December 2011 20:02, Mark Brown

...

If the API change is only in -next this shouldn't have been applied to the ASoC tree at all.  This needs go along with the change that adds the new API otherwise you break bisection.  Things like this *really* need to be made clear when posting patches.

I did mention that the patch series addresses the issue seen on -next tree in the cover letter. And I replied your query as below.

You shouldn't rely on cover letters getting noticed, they're too easy to disassociate from the patch.

...

With patches like this you really need to supply more context - knowing which release the commit you're talking about appears in is useful for exammple,

This patch only applies to -next, as the offending patch only sits on -next.

Yeah, that was after I'd applied the patch.

TBH given that this is an incompatible API change the original patch relly ought to be updating all users, there shouldn't be separate patches for the drivers.