From: Borislav Petkov <bp@alien8.de>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Wim Van Sebroeck <wim@iguana.be>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-watchdog@vger.kernel.org, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
Date: Wed, 27 Feb 2013 17:46:10 +0100 [thread overview]
Message-ID: <20130227164610.GG5530@pd.tnic> (raw)
In-Reply-To: <CA+icZUVhfYHu_EtC=itTR04OGq_yOq902_ZMb9_Jy=1pZfU_FA@mail.gmail.com>
On Wed, Feb 27, 2013 at 05:14:04PM +0100, Sedat Dilek wrote:
> I am not screaming or whining... people should reflect a bit on the
> patch workflow process? Also, I am sure a patchwork-service especially
> for -next is helpful.
Ok, now this formulation reads much nicer. So if you really think this
is needed, simply talk to sfr and see what he has to say about it. But
please do it in a nice way.
I'd say, serious suggestions on how the workflow could be improved are
always welcome.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-02-27 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 11:13 [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ] Sedat Dilek
2013-02-27 11:57 ` Wim Van Sebroeck
2013-02-27 12:23 ` Borislav Petkov
2013-02-27 12:51 ` Sedat Dilek
2013-02-27 13:08 ` Sedat Dilek
2013-02-27 15:07 ` Tejun Heo
2013-02-27 15:56 ` Sedat Dilek
2013-02-27 16:08 ` Borislav Petkov
2013-02-27 16:14 ` Sedat Dilek
2013-02-27 16:46 ` Borislav Petkov [this message]
2013-02-28 7:24 ` Sedat Dilek
2013-02-28 7:27 ` Sedat Dilek
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=20130227164610.GG5530@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=wim@iguana.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).