public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: RFC: [2.6 patch] drivers/media/video/ cleanups
Date: Tue, 9 Nov 2004 01:43:41 +0100	[thread overview]
Message-ID: <20041109004341.GO15077@stusta.de> (raw)
In-Reply-To: <20041108114008.GB20607@bytesex>

On Mon, Nov 08, 2004 at 12:40:08PM +0100, Gerd Knorr wrote:
> On Sun, Nov 07, 2004 at 06:50:17PM +0100, Adrian Bunk wrote:
> > the patch below contains several cleanups for drivers/media/video/, most 
> > of them are:
> > - needlessly global code made static
> > - currenly unused code removed
> 
> No, not this way in one big blob please.  It would be very nice if you
> can split that into smaller pieces:
> 
>   (1) The ObviouslyCorrect stuff, i.e. make stuff static which isn't
>       declared in any header file.
>   (2) The stuff which needs some more careful review (drop functions,
>       drop stuff from header files, ...).
> 
> Especially the later please splitted by driver, so the driver
> maintainers can have a look (which is kida problematic for some v4l
> drivers as there is no active maintainer currently, but I'd prefeare
> to have that separately in my inbox neverless).

OK, the patches follow as followups to this mail.

> I don't like your attitude to just drop stuff as "cleanup".  If
> functions are declared in a header file they are usually for a reason,
> thus that kind of stuff needs some careful checking whenever these
> reasons still exist or not.  Not every function which isn't used at the

That's why I prefixed the subject with "RFC"...

> moment automatically is useless.  cx88_risc_disasm() for example is
> useful for debugging the driver.  And that there is no in-kernel user

But couldn't this be #if 0'ed?

This way it was easily available for developers, but wouldn't use space 
for all users.

> for exported functions doesn't mean that nobody uses it.  The stuff
> exported by bttv-if is used by lirc for example.

I've removed the bttv-if changes from the patches.

BTW: Can't lirc be included in the main kernel?

>   Gerd

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-11-09  0:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07 17:50 RFC: [2.6 patch] drivers/media/video/ cleanups Adrian Bunk
2004-11-08 11:40 ` Gerd Knorr
2004-11-09  0:43   ` Adrian Bunk [this message]
2004-11-09  0:50     ` [1/11] drivers/media/video: the easy cleanups Adrian Bunk
2004-11-09  0:51     ` [2/11] media/video/msp3400.c: remove unused struct d1 Adrian Bunk
2004-11-09  0:53     ` [3/11] zoran_driver.c: make zoran_num_formats static Adrian Bunk
2004-11-09  0:55     ` [4/11] bttv-cards.c: remove unused function bttv_reset_audio Adrian Bunk
2004-11-09  0:57     ` [5/11] bttv-risc.c: make some functions static Adrian Bunk
2004-11-09  0:59     ` [6/11] v4l2-common.c: remove v4l2_video_std_fps Adrian Bunk
2004-11-09  1:00     ` [7/11] bttv-driver.c: make some variables static Adrian Bunk
2004-11-09  1:02     ` [8/11] saa7134-core.c: make saa7134_devcount static Adrian Bunk
2004-11-09  1:03     ` [9/11] bttv-i2c.c: make two functions static Adrian Bunk
2004-11-09  1:05     ` [10/11] zoran_device.c: make zr36057_init_vfe static Adrian Bunk
2004-11-09  1:07     ` [11/11] misc bttv statification Adrian Bunk
2004-11-09  9:46     ` RFC: [2.6 patch] drivers/media/video/ cleanups Gerd Knorr
2004-11-10  2:32       ` [2.6 patch] #if 0 cx88_risc_disasm Adrian Bunk

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=20041109004341.GO15077@stusta.de \
    --to=bunk@stusta.de \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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