2012/8/10 John W. Linville <linville@xxxxxxxxxxxxx>: > On Fri, Aug 10, 2012 at 02:25:48PM +0200, Rafał Miłecki wrote: >> 2012/8/10 Hauke Mehrtens <hauke@xxxxxxxxxx>: >> > On 08/10/2012 11:32 AM, Rafał Miłecki wrote: >> >> 2012/8/10 Arend van Spriel <arend@xxxxxxxxxxxx>: >> >>> On 08/09/2012 10:38 PM, Rafał Miłecki wrote: >> >>>> This allows drivers to access flash conditionally and stop crashing some >> >>>> devices. >> >>>> >> >>>> Signed-off-by: Rafał Miłecki <zajec5@xxxxxxxxx> >> >>>> Acked-by: Hauke Mehrtens <hauke@xxxxxxxxxx> >> >>>> --- >> >>>> John: I suggest taking it for wirelesss, AKA fix >> >>> >> >>> Maybe you could mentioned devices and/or drivers crashes without this patch? >> >> >> >> Yes, sure! The problematic one for me is arch/mips/bcm47xx/nvram.c. >> >> Right now it assumes every BCMA board has pflash. I'll submit fix for >> >> mips tree when this patch hits it. >> > >> > Letting this patches get merged into the wireless tree and an other >> > patches which depends on this one into the mips tree will cause >> > problems, because the wireless tree only gets merged into the mips tree >> > indirectly round about the rc1 release in form of the rc1 release done >> > by Linus. >> > >> > The patch to arch/mips/bcm47xx/nvram.c will depend on this one and you >> > should submit them to the same tree. >> >> I'm planning to wait until rc2 (or rc3 if needed). I know the dependency :) > > Which rc2? Because Ralf probably won't have it in his tree until > the 3.7-rc1 timeframe... Ouch, I hoped bcma fix will go into 3.6-rc2 or 3.6-rc3 and Ralf will rebase his tree against Linus at some point... OK, I'll try to send additional bcm47xx fix through yours tree (after Ralf accepts it). -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
