Messages in this thread | | | Subject | Re: [git pull] Fixes to 2.6.30rc2 | From | Eric Anholt <> | Date | Sun, 19 Apr 2009 23:00:24 -0700 |
| |
On Sun, 2009-04-19 at 16:47 +1000, Dave Airlie wrote: > On Sun, Apr 19, 2009 at 6:23 AM, Eric Anholt <eric@anholt.net> wrote: > > On Sat, 2009-04-18 at 01:59 -0700, David Miller wrote: > >> From: Eric Anholt <eric@anholt.net> > >> Date: Fri, 17 Apr 2009 13:49:59 -0700 > >> > >> > git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel drm-intel-next > >> > >> Eric, any plans to ever push your work through David Airlie's DRM > >> tree? I've been watching this for a few weeks and I'm mystified why > >> the Intel DRM drier stuff is so special that is always goes seperate. > >> > >> It's seems foolish for David to manage the infrastructure and core DRM > >> changes, as well as those for radeon and the other drivers other than > >> Intel, which could potentially cause merge issues and conflicts with > >> your driver changes. > >> > >> Why not do Intel DRM driver development via his tree? I just don't > >> get it. :-/ > > > > Inside of the merge window, I am going through Dave again because he > > requested it (though delays meant that I didn't get a major cleanup in > > this merge window). However, Dave is also quite busy, and not stealing > > his time every few days to pull my tree for just forwarding bugfixes on > > seems to be a win. > > btw which cleanup, I seem to remember it arriving after the merge > window had opened. > > The theory is the code was in my tree before Linus opened the window > or it doesn't > get
Yeah, it was early merge window iirc, the mechanical drm_malloc/drm_calloc/drm_free nuke. It really needs to die. In a fire.
-- Eric Anholt eric@anholt.net eric.anholt@intel.com
[unhandled content-type:application/pgp-signature] | |