From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Date: Mon, 30 Oct 2017 09:52:07 +0000 Subject: Re: [PATCH 1/2] drm/rcar-du: Use common error handling code in rcar_du_encoders_init() Message-Id: <87d155gdyw.fsf@intel.com> List-Id: References: <7d5e68c7-2d64-0131-1a08-eeb4e03cc113@users.sourceforge.net> <9fafa688-f699-c587-ef77-840efa71bf76@users.sourceforge.net> <87tvyke8g2.fsf@intel.com> <1864580.oVLIQZJ4NS@avalon> In-Reply-To: <1864580.oVLIQZJ4NS@avalon> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Laurent Pinchart Cc: SF Markus Elfring , dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, David Airlie , kernel-janitors@vger.kernel.org, LKML , Sean Paul , Daniel Vetter On Sun, 29 Oct 2017, Laurent Pinchart wrote: > Hi Jani, > > On Friday, 27 October 2017 21:45:17 EET Jani Nikula wrote: >> On Tue, 24 Oct 2017, SF Markus Elfring wrote: >> > Add a jump target so that a bit of exception handling can be better reused >> > at the end of this function. >> > >> > This issue was detected by using the Coccinelle software. >> >> Please also look into the GCC software, which will detect that your >> patch does not compile. > > Just for the record, I've been bitten in the past by applying one of Markus' > patches that seemed to make sense, only to discover later that it introduced a > security hole. I now drop his patches altogether, so could you please keep an > eye open to make sure none of them touching the rcar-du driver will be applied > through drm-misc ? Ack. You're the maintainer, and we need to respect that. In general, I'll pick up any patches that are good, but the current track record is that Markus' patches need extra scrutiny, and many of the patches contain subjective changes that lead to debate that is not constructive. There's no return on investment here. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center