From: mkrufky@linuxtv.org
To: xyzzy@speakeasy.org
Cc: bunk@kernel.org, toralf.foerster@gmx.de,
v4l-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com,
linux-kernel@vger.kernel.org, mchehab@infradead.org
Subject: Re: [v4l-dvb-maintainer] [2.6 patch] drivers/media/Makefile: alwa ys enter video/
Date: Wed, 12 Dec 2007 16:16:04 -0500 [thread overview]
Message-ID: <47604F94.6060706@linuxtv.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0712121310330.111@shell2.speakeasy.net>
Trent Piepho wrote:
> On Wed, 12 Dec 2007, Adrian Bunk wrote:
>
>>> I don't see any issue on making both dependent on VIDEO_TUNER for
>>> 2.6.24, since they are currently used only by tuner core module
>>> (tuner.ko).
>>> ...
>>>
>> If "selected code isn't included" also counts as a bug at least dabusb
>> is also affected by the same bug.
>>
>
>
>> What about the patch below instead that fixes the actual bug instead of
>> working around it?
>>
>
> Pretty much exactly the same as the patch I posted on Oct 19th. Some
> people like to make things harder than they need to be.
>
> http://article.gmane.org/gmane.comp.video.video4linux/35274
Interesting. I've no idea why I never received that email from you, Trent.
Whomever invented email should be shot. :-P
Please push this in.
-Mike
next prev parent reply other threads:[~2007-12-12 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 8:34 build #340 failed for 2.6.24-rc5-g75b8c13 in linux/drivers/media/video/tuner.ko Toralf Förster
2007-12-12 13:42 ` [v4l-dvb-maintainer] " Michael Krufky
2007-12-12 14:46 ` Mauro Carvalho Chehab
2007-12-12 16:00 ` mkrufky
2007-12-12 17:57 ` [v4l-dvb-maintainer] build #340 failed for 2.6.24-rc5-g75b8c13 in?linux/drivers/media/video/tuner.ko Adrian Bunk
2007-12-13 20:11 ` Mauro Carvalho Chehab
2007-12-12 18:40 ` [2.6 patch] drivers/media/Makefile: always enter video/ Adrian Bunk
2007-12-12 21:13 ` [v4l-dvb-maintainer] " Trent Piepho
2007-12-12 21:16 ` mkrufky [this message]
2007-12-13 9:55 ` Mauro Carvalho Chehab
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=47604F94.6060706@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=toralf.foerster@gmx.de \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
--cc=xyzzy@speakeasy.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