Hi, On Fri, Jan 29, 2016 at 1:52 PM, Olof Johansson <olof@xxxxxxxxx> wrote: > On Tue, Jan 26, 2016 at 4:39 PM, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: >> Hi, >> >> On Tue, Jan 26, 2016 at 3:59 PM, Andrew Morton >> <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >>> On Mon, 11 Jan 2016 09:30:22 -0800 Douglas Anderson <dianders@xxxxxxxxxxxx> wrote: >>> >>>> This series of patches will speed up memory allocation in dma-mapping >>>> quite a bit. >>> >>> This is pretty much all ARM and driver stuff so I think I'll duck it. >>> But I can merge it if nobody else feels a need to. >> >> I was going to ask what the next steps were for this series. >> Presumably I could post the patch to Russell's patch tracker if folks >> want me to do that. Alternatively it could go through the ARM-SOC >> tree? >> >> >>> I saw a few acked-by/tested-by/etc from the v5 posting which weren't >>> carried over into v6 (might have been a timing race), so please fix >>> that up if there's an opportunity. >> >> Right. Both Robin and Tomasz gave their Reviewed-by to Patch #1 in v5 >> even after v6 was posted. >> >> >>> Regarding the new DMA_ATTR_ALLOC_SINGLE_PAGES hint: I suggest adding >>> "DMA_ATTR_ALLOC_SINGLE_PAGES is presently implemented only on ARM" to >>> the docs. Or perhaps have a shot at implementing it elsewhere. >> >> Warning sounds good. >> >> >>> Typo in 4/5 changelog: "reqiurements" >> >> Thanks for catching! >> >> >> I'm happy to post up a v6 with these things fixed or I'm happy for >> whoever is applying it to make these small fixes themselves. Any >> volunteers? Olof, Arnd, or Russell: any of you want these patches? > > I think it makes sense to send these through Russell's tracker for him > to merge, especially since I don't think there are any dependencies on > them for SoC-specific patches coming up. Sounds good. I'll make the nitfixes and I'll post a v7 directly to Russell's tracker. I'll follow up here with a link to those patches. -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
