From: Michal Marek <mmarek@suse.cz>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] modpost: fix segfault with short symbol names
Date: Mon, 14 Dec 2009 17:32:52 +0100 [thread overview]
Message-ID: <4B2668B4.8080005@suse.cz> (raw)
In-Reply-To: <51737.84.105.60.153.1260797592.squirrel@gate.crashing.org>
On 14.12.2009 14:33, Segher Boessenkool wrote:
> So the patch fixes a real problem. I'm sorry for being dense.
>
> Acked-by: Segher Boessenkool <segher@kernel.crashing.org>
Thanks :). Rusty, I sent the patch to you because you have some other
modpost stuff in the rr tree. But I can add it to the kbuild tree as
well if you want.
Michal
next prev parent reply other threads:[~2009-12-14 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 11:02 [PATCH] modpost: fix segfault with short symbol names Michal Marek
2009-12-12 15:26 ` Segher Boessenkool
2009-12-14 10:06 ` Michal Marek
2009-12-14 12:29 ` Segher Boessenkool
2009-12-14 13:33 ` Segher Boessenkool
2009-12-14 16:32 ` Michal Marek [this message]
2009-12-15 5:14 ` Rusty Russell
2009-12-14 23:41 ` Rusty Russell
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=4B2668B4.8080005@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=segher@kernel.crashing.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).