From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Date: Wed, 07 Oct 2020 15:41:41 +0000 Subject: Re: [PATCH 1/3] fbdev/sbuslib: remove FBIOSCURSOR/FBIOGCURSOR leftovers Message-Id: <20201007154141.GA862107@ravnborg.org> List-Id: References: <20201007074447.797968-1-hch@lst.de> <20201007074447.797968-2-hch@lst.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Arnd Bergmann Cc: Christoph Hellwig , Geert Uytterhoeven , "David S. Miller" , Bartlomiej Zolnierkiewicz , linux-m68k , sparclinux , Linux Fbdev development list Hi Arnd. On Wed, Oct 07, 2020 at 10:54:19AM +0200, Arnd Bergmann wrote: > On Wed, Oct 7, 2020 at 9:44 AM Christoph Hellwig wrote: > > > > There are no actual implementations of FBIOSCURSOR/FBIOGCURSOR left, so > > don't bother with a compat handler for it, and remove the remaining > > definitions as well. > > > > Signed-off-by: Christoph Hellwig > > I had submitted a similar patch earlier, and Sam Ravnborg applied it to the > drm-misc tree, but it doesn't seem to be in linux-next, so I don't know > what the state is. > > My version only removed the compat handling, not the data structures, > so I'm happy to see your version used instead if mine got lost. > > Acked-by: Arnd Bergmann I think the patches got applied to drm-misc-next *after* the final push to -next for the current merge window. So the patches are lingering in drm-misc-next waiting for the upcoming merge window to comple before they are pushed to linux-next. So for now the patches are only visible if one pulls drm-misc and checks out drm-misc-next branch. Pulling a fresh drm-misc tree just to be 100% sure ....... Yep, patches are there when I pull a fresh tree and mripard just confirmed on irc that he sees them in his drm-misc-next repo. I am working with git.freedesktop.org/git/drm/drm-misc. Sam