From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932512AbbD0JQs (ORCPT ); Mon, 27 Apr 2015 05:16:48 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:60187 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752909AbbD0JQp (ORCPT ); Mon, 27 Apr 2015 05:16:45 -0400 From: Arnd Bergmann To: Robert Jarzmik Cc: linux-arm-kernel@lists.infradead.org, Daniel Mack , Haojian Zhuang , linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 0/3] Fix lubbock and mainstone interrupts Date: Mon, 27 Apr 2015 11:16:17 +0200 Message-ID: <5225589.tkUhR6vGoM@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <87pp6rkzha.fsf@belgarion.home> References: <1429996403-13644-1-git-send-email-robert.jarzmik@free.fr> <7247485.mMzWTjWY84@wuerfel> <87pp6rkzha.fsf@belgarion.home> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:+WRfGDYgESGfU86a1eBKxhYlxxCCILrxAM3y6EmZjEITwvhM2vU 3ghMUFJY5X/R+hbqiOW/jMDR7k7jlazMCbLrIv9bKdYbOCUQgkpqQE+tzBXmz6SNn5hdD/+ 12lTDeCrm2XksUY9ta0iM+Br2P2+iLm7cwPWyqAzbCq0psDEp9I2ws7nD3nalV480gXw0aE aHi/fxvl6hs+YkFvwrpqA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sunday 26 April 2015 11:31:13 Robert Jarzmik wrote: > Arnd Bergmann writes: > > > On Saturday 25 April 2015 23:13:20 Robert Jarzmik wrote: > >> This serie was submitted to the lak list, then migrated to mfd drivers, to end > >> up again here. There was no change since last submission. Let's hope this is the > >> last spin and that these platform will be fixed at last. > >> > > > > Should these be marked 'Cc: stable@vger.kernel.org'? > I can do this. I thought that 3 patches of 100+ lines, and the fact that these > boards were broken since october 2011 would prevent this serie from reaching the > stable branch. > > Well, I'll resubmit with this information, and after comments stage it to my > fixes branch. Let's see what stable tree people will do. > > > Can you also add a 'Fixes' tag with the commit that introduced the problem? > Sure. You are right about the size limit, I didn't see how big the patches actually are. In this case, leave the 'Fixes' tag, but don't add the Cc to stable. Arnd