public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Niv Sardi <xaiki@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] remove forward declarations for ioctl helpers; let "noinline" do the work
Date: Wed, 20 Feb 2008 15:03:26 +1100	[thread overview]
Message-ID: <20080220040326.GC69752007@melbourne.sgi.com> (raw)
In-Reply-To: <20080210050446.GA12398@infradead.org>

* Christoph Hellwig <hch@infradead.org> [2008-02-10 00:04:46 -0500]:

> On Sat, Feb 09, 2008 at 01:42:42PM -0600, Eric Sandeen wrote:
> > (if this one is too purely cosmetic I won't be offended)
> > 
> > The forward declarations for the xfs_ioctl() helpers and
> > the associated comment about gcc behavior really aren't
> > needed; all of these functions are marked STATIC which
> > includes noinline, and the stack usage won't be a problem.
> > 
> > This effectively just removes the forward declarations and
> > moves xfs_ioctl() back to the end of the file.
> 
> Fine in generaly, but I'm a bit worried about the too cosmetic one.
> If the gods at sgi decide it's worth it please get it in ASAP (and
> that includes 2.6.25).
> 
> > 
> > Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
> > 
> > ---
> > 
> >  xfs_ioctl.c |  563 ++++++++++++++++----------------------
> >  1 files changed, 255 insertions(+), 308 deletions(-)

Less code same features, can only be good, I'll push it to -dev

Cheers,
-- 
Niv

      reply	other threads:[~2008-02-20  4:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 19:42 [PATCH] remove forward declarations for ioctl helpers; let "noinline" do the work Eric Sandeen
2008-02-10  5:04 ` Christoph Hellwig
2008-02-20  4:03   ` Niv Sardi [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=20080220040326.GC69752007@melbourne.sgi.com \
    --to=xaiki@sgi.com \
    --cc=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --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