From: Amerigo Wang <amwang@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com,
hch@infradead.org, mingo@elte.hu, akpm@linux-foundation.org
Subject: Re: [Patch 4/5] module: trim exception table in module_free()
Date: Thu, 04 Jun 2009 16:57:06 +0800 [thread overview]
Message-ID: <4A278C62.8000801@redhat.com> (raw)
In-Reply-To: <200906041800.54696.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Thu, 4 Jun 2009 11:16:37 am Amerigo Wang wrote:
>
>> Just as the comment said, trim the exception table entries when
>> module_free() mod->module_init.
>>
>> Currently, this is only done for x86. Other platforms should
>> also fix it like this (except sparc32).
>>
>
> I've taken this one to make it more generic. I'll leave the x86 maintainers
> to apply the rest.
>
Thank you. But this one depends on the previous, I don't think you can
apply this without
the previous ones.
It's better to let Ingo take all of these, of coures, if he thinks they
are fine. :)
next prev parent reply other threads:[~2009-06-04 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 1:46 [Patch 0/5][V2] module: merge module_32.c and module_64.c Amerigo Wang
2009-06-04 1:46 ` [Patch 1/5] x86 module: merge the same functions in " Amerigo Wang
2009-06-04 1:46 ` [Patch 2/5] x86 module: merge the rest functions with macros Amerigo Wang
2009-06-04 1:46 ` [Patch 3/5] uml module: fix uml build process due to this merge Amerigo Wang
2009-06-04 1:46 ` [Patch 4/5] module: trim exception table in module_free() Amerigo Wang
2009-06-04 8:30 ` Rusty Russell
2009-06-04 8:57 ` Amerigo Wang [this message]
2009-06-05 15:08 ` Rusty Russell
2009-06-08 1:28 ` Amerigo Wang
2009-06-10 8:09 ` David Miller
2009-06-07 12:15 ` Ingo Molnar
2009-06-08 1:36 ` Amerigo Wang
2009-06-09 7:51 ` Rusty Russell
2009-06-04 1:46 ` [Patch 5/5] module: merge module_alloc() finally Amerigo Wang
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=4A278C62.8000801@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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