On Wed, Jun 3, 2009 at 10:53, Mark Brown wrote:> On Wed, Jun 03, 2009 at 08:37:54AM -0400, Mike Frysinger wrote:>> On Wed, Jun 3, 2009 at 06:52, Mark Brown wrote:>> > However, given that this fix has missed two kernel releases due to the>> > very slow rate of responses to review comments I've applied it so users>> > get the benefit of the bug fix.>> not sure what you're referring to>> This looks like a respin of a fix which was originally submitted back in> 2.6.29 era or so. IIRC there's been two or three versions, each of> which needed fixes. it could be. i was going by the changes that werent in 2.6.30. ithought i looked for previous submissions, but i must have missedprevious attempts. i'm not familiar with alsa stuff, so i'm notalways sure when i need to bang on Cliff to get things fixed up(changes split / better comments / etc...). >> > Things would go more smoothly if you>> > could get new versions of patches submitted faster after the original>> > review.>>> the previous Blackfin kernel maintainer changed jobs so we've been>> transitioning. reality is, this doesnt happen over nite.>> I appreciate that Brian leaving won't have helped here but this was an> issue before then, it feels like there's some sort of general process> issue going on. I'm not sure what it is - IIRC there tends to be about> one set of Blackfin patches per kernel release.>> It's not specifically causing me problems, it's more of a concern from> the point of view of getting stuff to users. if fixes miss a merge window, then that's an issue. but in general,users only see fixes per release, so sending things more quickly therewouldnt really help ?-mike_______________________________________________Alsa-devel mailing listAlsa-devel@xxxxxxxxxxxxxxxxxxxx://mailman.alsa-project.org/mailman/listinfo/alsa-devel
