From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754188AbbINMrg (ORCPT ); Mon, 14 Sep 2015 08:47:36 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:36004 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751421AbbINMre (ORCPT ); Mon, 14 Sep 2015 08:47:34 -0400 Date: Mon, 14 Sep 2015 14:47:29 +0200 From: Ingo Molnar To: Sedat Dilek Cc: Peter Zijlstra , Baoquan He , Denys Vlasenko , Tejun Heo , Christoph Lameter , LKML , Andrew Morton , David Rientjes , Linus Torvalds , Thomas Gleixner , Thomas Graf , the arch/x86 maintainers , llvmlinux@lists.linuxfoundation.org Subject: Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference) Message-ID: <20150914124729.GA29030@gmail.com> References: <20150909125424.GP3644@twins.programming.kicks-ass.net> <20150914071231.GM18489@twins.programming.kicks-ass.net> <20150914085425.GN18489@twins.programming.kicks-ass.net> <20150914093550.GB24362@gmail.com> <20150914095903.GA865@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Sedat Dilek wrote: > On Mon, Sep 14, 2015 at 11:59 AM, Ingo Molnar wrote: > > > > * Sedat Dilek wrote: > > > >> From my side... How can the correbolation be improved...? > > > > The best workflow would be for someone to send patches that are considered > > clean enough. > > What do you mean by "patches that are considered clean"? > > "Clean" in the sense of is-not-a-hackery and/or > patch-does-not-follow-Linux-kernel-development-guidelines [1]? Both in the end. > Oh, if we all would follow Peter H. blog-article "On commit messages" [2]. > ( /me dreams of a better world. ) So if _you_ start sending those patches then you need to fix known problems. You don't have to keep the patches as-is as you found them, you are free to fix them, open source and all that. Just start simple, with a single, obvious looking patch, and we'll see from there on? Thanks, Ingo