From: linux@MichaelGeng.de (Michael Geng)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, kraxel@bytesex.org
Subject: Re: [ANNOUNCE] new driver for teletext decoder SAA5246A
Date: Wed, 25 Feb 2004 23:29:02 +0100 [thread overview]
Message-ID: <20040225222902.GA1259@t-online.de> (raw)
In-Reply-To: <20040225133647.1a9a3231.akpm@osdl.org>
> Yup. I was suggesting remmoval of the `inline' keyword, rather than
> actually moving the bodies of those functions into the caller.
>
> I've previously seen significant code size reductions by _not_ inlining
> large functions which had a single call site - just leave them as normal
> out-of-line functions. So it worth experimenting with - pretty simple to
> do. But if you're using a recent gcc it's probably inlining the function
> even when it's not marked inline. Whatever.
Sorry for the misunderstanding. I now tested code size with and without
the inline keyword. It's as you said: In some cases code size increases
in some cases it stays the same, in some cases size decreases. I removed
2 inline statements, this reduced the code size by 34 bytes. It's really
worth experimenting with the inline keyword.
The newly updated patch is located at
http://www.michaelgeng.de/linux/saa5246a-rev2-2.6.3.patch
> > If you want to add the patch, how about the following changelog:
> >
> > [V4L]: Added new driver for Teletext decoder SAA5246A from Philips
next prev parent reply other threads:[~2004-02-25 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 11:34 [ANNOUNCE] new driver for teletext decoder SAA5246A Michael Geng
[not found] ` <20040225041330.51961b28.akpm@osdl.org>
2004-02-25 18:10 ` Michael Geng
2004-02-25 21:36 ` Andrew Morton
2004-02-25 22:29 ` Michael Geng [this message]
[not found] ` <403CFBD9.2000607@convergence.de>
2004-02-25 21:11 ` Michael Geng
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=20040225222902.GA1259@t-online.de \
--to=linux@michaelgeng.de \
--cc=akpm@osdl.org \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox