Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752373AbaLSKsq (ORCPT ); Fri, 19 Dec 2014 05:48:46 -0500 Received: from cantor2.suse.de ([195.135.220.15]:57298 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751317AbaLSKsp (ORCPT ); Fri, 19 Dec 2014 05:48:45 -0500 Date: Fri, 19 Dec 2014 11:48:43 +0100 (CET) From: Jiri Kosina To: Benjamin Tissoires cc: Peter Wu , Nestor Lopez Casado , linux-input , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 2/3] HID: logitech-{dj,hidpp}: check report length In-Reply-To: Message-ID: References: <1418691016-30681-1-git-send-email-peter@lekensteyn.nl> <1418691016-30681-3-git-send-email-peter@lekensteyn.nl> <9001812.kk9brShn75@al> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 16 Dec 2014, Benjamin Tissoires wrote: > This is my personal opinion and Jiri can say something different. I > tend not to send big patches while there is a window opened. Sometimes > Jiri has the time to get through them, sometime he does not. > In this case, I think the patches you sent should be in the bugs fixes > categories, and, IMO should make into 3.19-rc1 or 3.19-rc2 (especially > the length check which could lead to CVEs if not tackled soon enough). > For these kind of things there is no timing, and the sooner the > better. > That being said, make sure that you keep track of those patches in > case they get lost for obvious reasons and be prepared to remind about > them if they do not make their way in Jiri's tree. > > Jiri, comments? I don't mind patches being sent during a merge window, it doesn't disturb my workflow. But it's always good to explicitly mark patches which are bugfixes and should go to -rc, so that I bump up the priority for reviewing them. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/