All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Baoquan He <bhe@redhat.com>, Denys Vlasenko <dvlasenk@redhat.com>,
	Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>, Thomas Graf <tgraf@suug.ch>,
	the arch/x86 maintainers <x86@kernel.org>,
	llvmlinux@lists.linuxfoundation.org
Subject: Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)
Date: Mon, 14 Sep 2015 14:47:29 +0200	[thread overview]
Message-ID: <20150914124729.GA29030@gmail.com> (raw)
In-Reply-To: <CA+icZUU4rgvxGwBN4CwFbJ6Gk4ZGxyrqU77vDkfP8gK9su0_Cg@mail.gmail.com>


* Sedat Dilek <sedat.dilek@gmail.com> wrote:

> On Mon, Sep 14, 2015 at 11:59 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * Sedat Dilek <sedat.dilek@gmail.com> 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

  reply	other threads:[~2015-09-14 12:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 17:45 [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference) Sedat Dilek
2015-09-07  5:58 ` Sedat Dilek
     [not found]   ` <CA+icZUUs3KEydWRgu_Y+YqS4TcCNp2DUw3Y+KfBzX7aPg_kzLw@mail.gmail.com>
2015-09-09  2:29     ` Baoquan He
2015-09-09  2:51       ` Sedat Dilek
2015-09-09  3:04         ` Sedat Dilek
2015-09-09  3:14           ` Sedat Dilek
2015-09-09  3:25         ` Baoquan He
2015-09-09  3:46           ` Sedat Dilek
2015-09-09  6:56             ` Sedat Dilek
2015-09-09  7:14               ` Baoquan He
2015-09-09  7:41                 ` Sedat Dilek
2015-09-09 10:05                   ` Sedat Dilek
2015-09-09 12:54                     ` Peter Zijlstra
2015-09-12 21:22                       ` Sedat Dilek
2015-09-13  2:33                         ` Sedat Dilek
2015-09-14  7:12                           ` Peter Zijlstra
2015-09-14  7:35                             ` Sedat Dilek
2015-09-14  7:57                               ` Sedat Dilek
2015-09-14  8:54                               ` Peter Zijlstra
2015-09-14  9:35                                 ` Ingo Molnar
2015-09-14  9:55                                   ` Sedat Dilek
2015-09-14  9:59                                     ` Ingo Molnar
2015-09-14 10:22                                       ` Sedat Dilek
2015-09-14 12:47                                         ` Ingo Molnar [this message]
2015-09-14  7:49                             ` Sedat Dilek
2015-09-14 17:50                               ` Austin S Hemmelgarn
2015-09-14 18:27                                 ` Christoph Lameter
2015-09-14 18:38                                   ` Austin S Hemmelgarn
2015-09-15  6:11                                   ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150914124729.GA29030@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=cl@linux.com \
    --cc=dvlasenk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvmlinux@lists.linuxfoundation.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=sedat.dilek@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tgraf@suug.ch \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.