From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934445AbcI0MTL (ORCPT ); Tue, 27 Sep 2016 08:19:11 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:50017 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933304AbcI0MTB (ORCPT ); Tue, 27 Sep 2016 08:19:01 -0400 Date: Tue, 27 Sep 2016 08:16:25 -0400 (EDT) From: Thomas Gleixner To: Dou Liyang cc: Mike Galbraith , Ingo Molnar , LKML , Borislav Petkov Subject: Re: [x86-tip] strange nr_cpus= boot regression In-Reply-To: Message-ID: References: <1474892945.9232.23.camel@gmail.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) 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, 27 Sep 2016, Dou Liyang wrote: > In fact, it's my fault. > I should re-base my patches after the commit c291b0151585 in time. Definitely not your fault. As a maintainer I should have been more careful and check whether Linus tree or x86/urgent has any modifications to that area before applying your patches. > I learned a lot from it. We all did. Thanks, tglx