public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Cyber Dog <cyberdog3k@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is DVB stuff compiling?
Date: Mon, 17 Oct 2005 23:07:16 -0400	[thread overview]
Message-ID: <435466E4.5020807@linuxtv.org> (raw)
In-Reply-To: <435465AC.3070506@linuxtv.org>

Michael Krufky wrote:

> Cyber Dog wrote:
>
>> #
>> # Multimedia devices
>> #
>> # CONFIG_VIDEO_DEV is not set
>>
>> #
>> # Digital Video Broadcasting Devices
>> #
>> # CONFIG_DVB is not set
>>
>> Which is what I would expect.  So why are these things compiling into
>> the kernel even if they're not selected? Or am I missing something
>> about the process?  Kernel 2.6.13.3 here.  Thanks.
>
> If you go look, you will notice that all of those built-in.o are zero 
> bytes large.  We've already fixed this in kernel 2.6.14 by preventing 
> the build of these empty units with the following patch (you can 
> safely apply it to 2.6.13.y):


I forgot to mention... You CAN apply the patch in my previous message if 
it bothers you enough, but it won't have any real affect on your kernel, 
as those built-in.o are all empty anyway.

>
> Don't build empty built-in.o when DVB/V4L is not configured.
> Thanks to Sam Ravnborg and Keith Owens.
>
> Signed-off-by: Johannes Stezenbach <js@linuxtv.org 
> <mailto:js@linuxtv.org>>

...and I hate it when Thunderbird does stuff like this when I cut&paste 
email addresses :-(

-- 
Michael Krufky


      reply	other threads:[~2005-10-18  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:29 Why is DVB stuff compiling? Cyber Dog
2005-10-18  3:02 ` Michael Krufky
2005-10-18  3:07   ` Michael Krufky [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=435466E4.5020807@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=cyberdog3k@gmail.com \
    --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