From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759806AbcAKWdA (ORCPT ); Mon, 11 Jan 2016 17:33:00 -0500 Received: from ozlabs.org ([103.22.144.67]:44074 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759347AbcAKWc7 (ORCPT ); Mon, 11 Jan 2016 17:32:59 -0500 Date: Tue, 12 Jan 2016 09:32:57 +1100 From: Stephen Rothwell To: Helge Deller Cc: Parisc List , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: strange commit in the parisc-hd tree Message-ID: <20160112093257.015545ec@canb.auug.org.au> In-Reply-To: <569422C8.4000706@gmx.de> References: <20160111092822.4b4c0233@canb.auug.org.au> <569422C8.4000706@gmx.de> X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Helge, On Mon, 11 Jan 2016 22:46:48 +0100 Helge Deller wrote: > > On 10.01.2016 23:28, Stephen Rothwell wrote: > > I noticed the following commit in the parisc-hd tree today: > > > > 43122681dd75 ("Fix __ARCH_SI_PREAMBLE_SIZE on parisc") > > > > which among other things says: > > > > This patch is not planned to be committed as it currently is. > > Right, I split it up into two. Good idea. > > [...] Please remove it from linux-next inclusion until it is ready. > > Sure, I just removed it now. Thanks. > > Delibeately introducing a patch to linux-next that may well cause build breakage > > in other architectures just before the merge window opens is a bit antisocial. > > That was in no way my intention. > In contrary, I wanted to see if other platforms are affected by the same bug without knowing. > Do you by any chance know if it broke some of the existing platforms? > If yes, that would be valuable info... No, because I took it out of linux-next yesterday. It is more a timing thing, if you had done that a few weeks ago, I would have just reported any build errors and continued on, but just before the merge window opens we don;t need the distraction. Also, if you can create another branch and give it to the zero day build farm, you should get better feed back. Also, linux-next is not supposed to contain patches without a Signed-off-by ... -- Cheers, Stephen Rothwell sfr@canb.auug.org.au