On Thu, Sep 13, 2012 at 4:00 PM, Takashi Iwai <tiwai at suse.de> wrote: > But, this makes me wonder why this patch can't go into 3.6. It's a > clear bug and the fix is trivial. > > Daniel, isn't it better to pick the fix (for 3.6) to drm-intel-fixes, > then merge back to drm-intel-next? Well, on a quick read-through it didn't sound serious (just a bit of noise in dmesg and a few spurious reconfigs), and we're rather late in the -rc cycle. Applying this on top of -fixes will cause a conflict, so didn't looked like I should bother. Also, I _want_ the patch for -next so that git blame shows the commit and not some random conflicting merge. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch