On Wed, Jul 12, 2017 at 2:54 PM, Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx> wrote: > On Wednesday, July 12, 2017 02:42:14 PM Daniel Vetter wrote: >> On Wed, Jul 12, 2017 at 12:41:34PM +0200, Bartlomiej Zolnierkiewicz wrote: >> > On Tuesday, July 11, 2017 04:52:19 PM Daniel Vetter wrote: >> > > Instead check info->ops->owner, which amounts to the same. >> > > >> > > Spotted because I want to remove the pile of broken and cargo-culted >> > > fb_info->flags assignments in drm drivers. >> > > >> > > v2: Fixup matrox (reported by kbuild). Also nuke FBINFO_FLAG_* defines >> > > that I've failed to spot. >> > > >> > > v3: Don't nuke FBINFO_FLAG_DEFAULT, that's used all over the place. >> > > >> > > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx> >> > > Cc: linux-fbdev@xxxxxxxxxxxxxxx >> > > Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxxx> >> > >> > Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx> >> >> Do you plan to pick these two patches up yourself, or do you expect me to >> merge them? > > Since the original patchset contained DRM changes (two last patches) > depending on fbdev changes (two first patches, the patch being discussed > was the second one) I assumed that you would like to take them all > through DRM tree. If this is not what is preferred, please tell me. There's no direct depency between 1&2 and 3&4, the only effect of merging them through separate trees is that the bootup logo might not show up when it's expected, until the trees are merged together. We could merge them through separate trees if you prefer that (I forgot to mention that in the cover letter), but I'm fine with putting them all into drm-misc with your ack for 4.14. Whatever you prefer, I don't mind either way. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
