If noone hers to them first poke me tomorrow. On an aircraft right now. Daniel Vetter <[email protected]> wrote: >On Fri, Jul 26, 2013 at 01:32:50PM -0700, Jesse Barnes wrote: >> These address the comments I've received so far, but omit the new >E820 >> type for this mem. >> >> Chris's patches could go on top if desired; they add a new type and >> resource reservation function for looking up regions by name. That >> allows us to remove some duplicate code in the driver for finding >stolen >> space. >> >> But I think these two are ready as-is. How should we merge them? >Just >> through the i915 tree since the first one touches our headers? that >and >> there probably won't be conflicts on the early-quirks file; that's >not >> touch too often... > >Just noticed that these patches aren't in -next yet - somehow I've >thought >they'd go in in through the x86 tree. > >Ingo et al: Should I merge these through drm-intel-next or will you >pick >them up? > >Thanks, Daniel
-- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
