From: Rusty Russell <rusty@rustcorp.com.au>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] module: Fix performance regression on modules with large symbol tables
Date: Tue, 08 Nov 2011 09:57:32 +1030 [thread overview]
Message-ID: <87d3d3secb.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAJiQ=7D4SSzzkPpPMGnaTq-wZXUGmXCRfKhYdPFg7APDu+VTwA@mail.gmail.com>
On Mon, 7 Nov 2011 11:58:08 -0800, Kevin Cernekee <cernekee@gmail.com> wrote:
> > I've started a separate patch to add comments to all this.
>
> Not sure how you want to handle combining these changes?
>
> I'll just send a V2 that rolls in all of the desired modifications, if
> there are no objections...
Please do. I'll write a comment patch on top of that, too.
Thanks!
Rusty.
next prev parent reply other threads:[~2011-11-08 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 0:48 [PATCH] module: Fix performance regression on modules with large symbol tables Kevin Cernekee
2011-11-07 1:29 ` Rusty Russell
2011-11-07 19:58 ` Kevin Cernekee
2011-11-07 23:27 ` Rusty Russell [this message]
2011-11-08 7:54 ` Jan Beulich
2011-11-08 21:30 ` 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=87d3d3secb.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=JBeulich@novell.com \
--cc=cernekee@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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