On Thursday 12 June 2008 07:18:32 FUJITA Tomonori wrote: > > Yeah ok. That's an unlikely error path. > > Yeah, it doesn't always happen, but it possible that it happens? Yes. I will create a new patch and send it to John Linville. So it will also quickly end up in the -mm tree, too. This will fix both bugs. > No, seems that there are some confusion. This is just in -mm to find > problems: > > http://userweb.kernel.org/~akpm/mmotm/broken-out/dma-mapping-add-the-device-argument-to-dma_mapping_error.patch > > This patch is a trivial but changes lots of places. So it's difficult > to get an ACK on all the places. Thanks a lot for explaining this. This makes things a lot easier. > This patch need several fixes but all the patches are trivial except > for b34. I guess that it is because b34 handles devices for It's called b43 ;) > dma-mapping in an uncommon way. Yeah, the hardware is pretty stupid, so we have lots of special workarounds and so on... So I hardly touch the DMA code and was very surprised about this bugreport. :) -- Greetings Michael. -- 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
