From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Pinchart Date: Fri, 13 Mar 2020 13:38:03 +0000 Subject: Re: [PATCH] omapfb: Remove unused writeback code Message-Id: <20200313133803.GA9070@pendragon.ideasonboard.com> List-Id: References: <20200313122410.7528-1-tomi.valkeinen@ti.com> <20200313132244.GB4751@pendragon.ideasonboard.com> <249364fc-bc83-6fe6-d3bf-f709505c299e@ti.com> In-Reply-To: <249364fc-bc83-6fe6-d3bf-f709505c299e@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Tomi Valkeinen Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, Bartlomiej Zolnierkiewicz Hi Tomi, On Fri, Mar 13, 2020 at 03:30:15PM +0200, Tomi Valkeinen wrote: > On 13/03/2020 15:22, Laurent Pinchart wrote: > > On Fri, Mar 13, 2020 at 02:24:10PM +0200, Tomi Valkeinen wrote: > >> Remove unused writeback code. This code will never be used, as omapfb is > >> being deprecated. > > > > I'm fine with that, but out of curiosity, is there any particular reason > > to remove that code now instead of letting omapfb bitrot slowly ? > > It conflicts with tidss's writeback code in TI kernel, when compiling tidss and omapfb into the > kernel. I thought this is the easiest way to resolve that, as all the removed code is dead code, > instead of trying to invent new names in tidss for a lot of functions. > > Probably the functions in tidss still could use some renaming in the future, but I didn't want to be > forced to do that because of omapfb's dead code... Could you do both ? :-) It's not good using too generic names in tidss. You can just prefix the functions with tidss_. There's a risk of conflict with omapdrm too if the names are too generic. > So, not a super good reason, but on the other hand, removing dead code is always a good thing. -- Regards, Laurent Pinchart