From: Mingming Cao <cmm@us.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] allocate struct ext4_allocation_context from a kmem cache to save stack space
Date: Fri, 08 Feb 2008 10:25:20 -0800 [thread overview]
Message-ID: <1202495120.15315.3.camel@localhost.localdomain> (raw)
In-Reply-To: <47AC8986.40409@redhat.com>
On Fri, 2008-02-08 at 10:55 -0600, Eric Sandeen wrote:
> Mingming Cao wrote:
>
> > printk could be removed...so as long as it builds fine. I had looked at
> > the history yesterday and find this fix
> > http://lists.openwall.net/linux-ext4/2007/10/10/2
> > so I was under impression that the ifdefs was added to fix compile
> > issue. I did not look more closely. Maybe that's not a issue any more.
>
> I guess I should look into it. For now let's just drop the #ifdef
> removal, it's not related anyway.
>
> Would you like me to send a fresh patch?
>
ah...not necessary, I can edit the patch when merge it to the queue.
Yes we could deal with the ifdef in a separate patch, maybe something
like suggested by Shaggy.
Regards,
Mingming
next prev parent reply other threads:[~2008-02-08 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 17:05 [PATCH] allocate struct ext4_allocation_context from a kmem cache to save stack space Eric Sandeen
2008-02-08 0:11 ` Mingming Cao
2008-02-08 1:06 ` Eric Sandeen
2008-02-08 1:37 ` Mingming Cao
2008-02-08 2:35 ` Eric Sandeen
2008-02-08 15:45 ` Dave Kleikamp
2008-02-08 16:39 ` Mingming Cao
2008-02-08 16:55 ` Eric Sandeen
2008-02-08 18:25 ` Mingming Cao [this message]
2008-02-08 18:43 ` Dave Kleikamp
2008-02-08 17:00 ` Dave Kleikamp
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=1202495120.15315.3.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=shaggy@linux.vnet.ibm.com \
/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