On Thu, Dec 24, 2009 at 11:40:18AM +0000, Mark Brown wrote: > On Thu, Dec 24, 2009 at 03:11:43PM +0900, Kuninori Morimoto wrote: > > > > No problem, feel free to add my ack to the combined patch. > > > I sent patch which is for SuperH platform, and Paul already applied it. > > I can find it on latest linus git (9f815a1765b0ce766ab1d26ef192d30410f70b2b). > > So sorry, can you please re-check this email ? > > [fsi-ak4642: Remove ak4642_add_i2c_device] > > Oh, what a shame. I'll apply the patch. I missed the rest of this discussion, but if your conerns are about bisection, it's not an issue in this case. Board patches that add i2c or platform device data with no unmet dependencies I usually merge early. The main rationale for this is that the driver often shows up quite a bit later, and the board code will likely have had more paches piled up on top of it and merge conflicts ensue. For patches that depend on headers and definitions added by the driver patch, we either apply them together, or I just hold off on the board patch until the driver is upstream. patchwork helps keep track of the ones that are still pending at least. These sorts of ordering issues happen a lot, but are generally always resolved by rc2. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
