From: Chris Mason <chris.mason@oracle.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Remove code duplication in comp_keys
Date: Fri, 24 Jul 2009 11:10:42 -0400 [thread overview]
Message-ID: <20090724151042.GE16192@think> (raw)
In-Reply-To: <200907240054.53667.diegocg@gmail.com>
On Fri, Jul 24, 2009 at 12:54:53AM +0200, Diego Calleja wrote:
> comp_keys is duplicating what is done in btrfs_comp_cpu_keys, so just
> call it.
Ok, looks like gcc is doing the right thing and inlining properly so
I've queued this one up.
-chris
prev parent reply other threads:[~2009-07-24 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 22:54 [PATCH] Remove code duplication in comp_keys Diego Calleja
2009-07-24 15:10 ` Chris Mason [this message]
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=20090724151042.GE16192@think \
--to=chris.mason@oracle.com \
--cc=diegocg@gmail.com \
--cc=linux-btrfs@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 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.