public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Niv Sardi <xaiki@sgi.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: TAKE streamline init/exit path
Date: Thu, 22 May 2008 17:56:16 +0200	[thread overview]
Message-ID: <20080522155616.GA7682@lst.de> (raw)
In-Reply-To: <ncc7ido2i1g.fsf_-_@sgi.com>

On Wed, May 21, 2008 at 06:11:23PM +1000, Niv Sardi wrote:
> 
> Christoph Hellwig <hch@lst.de> writes:
> 
> > Updated patch below.  There's now split out function to create/destroy
> > the kmem zones and alloc/free the trace buffers.  I've also changed the
> > ktrace allocations to KM_MAYFAIL and handled errors resulting from that.
> >
> > And yes, we really should replace the XFS_*_TRACE ifdefs with a single
> > XFS_TRACE..
> 
> Thanks, 
> 
> it's in, forgot to send the TAKE message to oss, here it comes:
> 
> Subject: TAKE 976035 -  streamline init/exit path
> 
> Date:  Wed, 21 May 2008 18:02:18 +1000
> Workarea:  chook.melbourne.sgi.com:/build/xaiki/isms/mangrove-1.3
> Inspected by:  hch

Well, mangrove was the sles10 NAS tree if I remember correctly.  And it
indeed hasn't made it to either the CVS or git tree on oss.sgi.com yet.

  reply	other threads:[~2008-05-22 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18 13:05 [PATCH] streamline init/exit path Christoph Hellwig
2008-05-21  0:41 ` Niv Sardi
2008-05-21  6:01   ` Christoph Hellwig
2008-05-21  7:01     ` Niv Sardi
2008-05-21  7:24       ` Christoph Hellwig
2008-05-21  8:11         ` TAKE " Niv Sardi
2008-05-22 15:56           ` Christoph Hellwig [this message]
2008-05-23  0:26             ` Barry Naujok
2008-05-23  1:57               ` Niv Sardi
2008-05-25 19:10               ` Christoph Hellwig

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=20080522155616.GA7682@lst.de \
    --to=hch@lst.de \
    --cc=xaiki@sgi.com \
    --cc=xfs@oss.sgi.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