LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Robin Getz <rgetz@blackfin.uclinux.org>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH [1/1]: Don't return symbol lables in init sections after they have been freed
Date: Sat, 5 Apr 2008 01:13:43 -0400 [thread overview]
Message-ID: <200804050113.43433.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <200804040941.42275.rusty@rustcorp.com.au>
On Thu 3 Apr 2008 19:41, Rusty Russell pondered:
> On Thursday 03 April 2008 08:01:25 Robin Getz wrote:
> > On Tue 4 Mar 2008 20:43, Rusty Russell pondered:
> > > As to the actual patch, your kallsyms.c patch matches
> > > a2da4052f1df6bc77749f84496fe731ab8b458f7's change to extable.c: please
> > > resubmit with just that one. For bonus points, look at combining the
> > > extable and kallsyms logic so we don't diverge in future...
> >
> > OK since this took so long, I went for bonus points...
>
> Looks good. I don't have extratext in my kernel tho
> (v2.6.25-rc8-139-ge315c12).
OK - for some reason - I tested the patch, sent it upstream, but it wasn't
kept in our local version when we updated to 2.6.24 :(
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a3b81113fb6658629f4ebaabf8dd3067cd341020
I'll update and send something new.
> Otherwise I'd suspect it should be consistently used between extable
> and kallsyms.
next prev parent reply other threads:[~2008-04-05 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 23:47 Robin Getz
2008-03-05 0:05 ` Andrew Morton
2008-03-06 5:13 ` Greg KH
2008-03-05 1:43 ` Rusty Russell
2008-03-05 17:53 ` Robin Getz
2008-04-02 22:01 ` Robin Getz
2008-04-03 23:41 ` Rusty Russell
2008-04-05 5:13 ` Robin Getz [this message]
2008-04-06 4:14 ` Robin Getz
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=200804050113.43433.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--subject='Re: PATCH [1/1]: Don'\''t return symbol lables in init sections after they have been freed' \
/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
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).