From: "George Spelvin" <linux@horizon.com>
To: bp@alien8.de, pablo@netfilter.org
Cc: gaofeng@cn.fujitsu.com, kaber@trash.net,
linux-kernel@vger.kernel.org, linux@horizon.com,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: v3.10-rc7 oops soon after boot
Date: 24 Jun 2013 18:17:08 -0400 [thread overview]
Message-ID: <20130624221708.15489.qmail@science.horizon.com> (raw)
In-Reply-To: <20130624161305.GC26766@pd.tnic>
>> Reported-by: Borislav Petkov <bp@alien8.de>
> This should be:
>
> Reported-by: George Spelvin <linux@horizon.com>
>
> I only connected the dots...
Well, you did a whole lot more than me! I just lobbed a "d'oh, it
crashes" into the seething ocean of lkml. (Admittedly, I had reason
to act fast: we're very close to release.)
You figured out what subsystem was at fault and got the right people
involved. Definitely a valuable contribution.
Me, personally, I don't give a flying f*** about such credit; I had
an itch and was trolling for someone to scratch it.
So feel free to take Reported-by (you are the one who reported it *to
someone who could fix it*), Triaged-by, or whatever.
next prev parent reply other threads:[~2013-06-24 22:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130624064934.24201.qmail@science.horizon.com>
2013-06-24 7:33 ` v3.10-rc7 oops soon after boot Borislav Petkov
2013-06-24 8:47 ` George Spelvin
2013-06-24 9:12 ` Gao feng
2013-06-24 9:41 ` George Spelvin
2013-06-24 9:52 ` Gao feng
2013-06-24 10:01 ` George Spelvin
2013-06-24 11:34 ` Pablo Neira Ayuso
2013-06-24 15:10 ` Pablo Neira Ayuso
2013-06-24 16:13 ` Borislav Petkov
2013-06-24 22:17 ` George Spelvin [this message]
2013-06-24 22:34 ` Borislav Petkov
2013-06-25 1:36 ` Gao feng
2013-06-25 6:17 ` Gao feng
2013-06-26 6:28 ` George Spelvin
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=20130624221708.15489.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=bp@alien8.de \
--cc=gaofeng@cn.fujitsu.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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