linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nitin Gupta <nitingupta910@gmail.com>
Cc: linux-kernel@vger.kernel.org, Richard Purdie <richard@openedhand.com>
Subject: Re: [RFC] LZO1X de/compression support
Date: Tue, 22 May 2007 12:34:07 +0300	[thread overview]
Message-ID: <4652B90F.2090004@cs.helsinki.fi> (raw)
In-Reply-To: <4cefeab80705220210s98c6784k76c9d9752676112a@mail.gmail.com>

Nitin Gupta wrote:
> Ok. I will make them inline functions now.

Btw, the only reason why any sane compiler would not inline
them is because it has reason to believe the end-result will
be more efficient. AFAIK you only need to use
__always_inline where it matters for correctness (like, for
example, in mm/slab.c) with GCC 4.0 and up.

  reply	other threads:[~2007-05-22  9:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  9:58 [RFC] LZO1X de/compression support Nitin Gupta
2007-05-18 10:14 ` Heikki Orsila
2007-05-18 11:27   ` Nitin Gupta
2007-05-18 11:53     ` Richard Purdie
2007-05-18 10:42 ` Pekka Enberg
2007-05-18 10:53   ` Pekka Enberg
2007-05-22  8:54   ` Nitin Gupta
2007-05-22  8:59     ` Pekka Enberg
2007-05-22  9:10       ` Nitin Gupta
2007-05-22  9:34         ` Pekka Enberg [this message]
2007-05-18 11:11 ` Andrey Panin
2007-05-22  9:08   ` Nitin Gupta
2007-05-22 19:44     ` Jan Engelhardt
2007-05-22 21:24     ` Bernd Petrovitsch
2007-05-23 16:35       ` Jeremy Fitzhardinge
2007-05-18 11:46 ` Richard Purdie
2007-05-22  9:19   ` Nitin Gupta
2007-05-18 20:04 ` Matt Mackall
2007-05-18 21:14 ` Krzysztof Halasa
2007-05-19 18:55   ` Bill Rugolsky Jr.
2007-05-19 21:52     ` Richard Purdie
2007-05-22 19:40 ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-05-19 18:12 devzero
2007-05-20 11:42 Tomasz Chmielewski

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=4652B90F.2090004@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitingupta910@gmail.com \
    --cc=richard@openedhand.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;
as well as URLs for NNTP newsgroup(s).