All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Amerigo Wang <amwang@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, jdike@addtoit.com,
	hch@infradead.org, akpm@linux-foundation.org
Subject: Re: [Patch 4/5] module: trim exception table in module_free()
Date: Tue, 9 Jun 2009 17:21:54 +0930	[thread overview]
Message-ID: <200906091721.59031.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A2C6B0E.9090702@redhat.com>

On Mon, 8 Jun 2009 11:06:14 am Amerigo Wang wrote:
> Ingo Molnar wrote:
> > I think it makes most sense to handle them together. We have no
> > interacting changes pending in the x86 tree, feel free to pick them
> > up.
>
> Thanks for clarifying.
>
> So, Rusty, could you please take all of these except patch 4/5? Since you
> have a much better one to replace that one. :)

Yep, I've put them in my tree for testing; if all goes well, they'll hit 
linux-next in a couple of days.

Thanks!
Rusty.

  reply	other threads:[~2009-06-09  7:52 UTC|newest]

Thread overview: 17+ 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
2009-06-05 15:08       ` Rusty Russell
2009-06-05 15:20         ` Rusty Russell
2009-06-08  1:28         ` Amerigo Wang
2009-06-08  1:28           ` Amerigo Wang
2009-06-10  8:09         ` David Miller
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 [this message]
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=200906091721.59031.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=amwang@redhat.com \
    --cc=hch@infradead.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.