From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751875AbdB0Pdi (ORCPT ); Mon, 27 Feb 2017 10:33:38 -0500 Received: from mail.kernel.org ([198.145.29.136]:49400 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbdB0Pdf (ORCPT ); Mon, 27 Feb 2017 10:33:35 -0500 Date: Mon, 27 Feb 2017 10:22:43 -0500 From: Steven Rostedt To: Jason Baron Cc: Sachin Sant , linux-next@vger.kernel.org, LKML , linuxppc-dev@ozlabs.org, Michael Ellerman Subject: Re: next-20170217 boot on POWER8 LPAR : WARNING @kernel/jump_label.c:287 Message-ID: <20170227102243.2172a8ea@gandalf.local.home> In-Reply-To: <20c53e88-acf5-4c4f-cea9-4dd8745814b5@akamai.com> References: <1dffdaac-be8b-0052-52d4-a65fed39f894@akamai.com> <02B52EFB-4608-47F3-A81C-B8B52DB11233@linux.vnet.ibm.com> <20c53e88-acf5-4c4f-cea9-4dd8745814b5@akamai.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; 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 On Tue, 21 Feb 2017 11:37:21 -0500 Jason Baron wrote: > Thanks for testing. We probably need something like the following to > make sure we don't hit this on other arches. Steve - I will send 4 > separate patches for this to get arch maintainers' acks for this? > I just got back from ELC, so sorry for the late reply. I think you can just send this as one patch, as it is a single fix. Cc each of the arch maintainers though. Unless you think it will have conflicts with other changes in those archs. But I'm assuming there wont be any conflicts. This is a fix for something that I just pushed to Linus, thus it can still get in after the merge window closes. -- Steve From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: next-20170217 boot on POWER8 LPAR : WARNING @kernel/jump_label.c:287 Date: Mon, 27 Feb 2017 10:22:43 -0500 Message-ID: <20170227102243.2172a8ea@gandalf.local.home> References: <1dffdaac-be8b-0052-52d4-a65fed39f894@akamai.com> <02B52EFB-4608-47F3-A81C-B8B52DB11233@linux.vnet.ibm.com> <20c53e88-acf5-4c4f-cea9-4dd8745814b5@akamai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20c53e88-acf5-4c4f-cea9-4dd8745814b5@akamai.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: "Linuxppc-dev" To: Jason Baron Cc: Sachin Sant , linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org, LKML List-Id: linux-next.vger.kernel.org On Tue, 21 Feb 2017 11:37:21 -0500 Jason Baron wrote: > Thanks for testing. We probably need something like the following to > make sure we don't hit this on other arches. Steve - I will send 4 > separate patches for this to get arch maintainers' acks for this? > I just got back from ELC, so sorry for the late reply. I think you can just send this as one patch, as it is a single fix. Cc each of the arch maintainers though. Unless you think it will have conflicts with other changes in those archs. But I'm assuming there wont be any conflicts. This is a fix for something that I just pushed to Linus, thus it can still get in after the merge window closes. -- Steve