public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Michael Hunold <hunold@linuxtv.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] v4l/dvb: cx88 driver update
Date: Fri, 17 Sep 2004 10:23:47 +0200	[thread overview]
Message-ID: <20040917082347.GB16344@bytesex> (raw)
In-Reply-To: <414A862F.5030200@linuxtv.org>

On Fri, Sep 17, 2004 at 08:37:35AM +0200, Michael Hunold wrote:
> Hi,
> 
>  On 17.09.2004 01:08, Andrew Morton wrote:
> >Gerd Knorr <kraxel@bytesex.org> wrote:
> 
> >>This is a major update of the cx88 driver.
> 
> >drivers/media/video/cx88/cx88-dvb.c:215: `FE_UNREGISTER' undeclared (first 
> >use in this function)

Whoops.  That wasn't intentional ...

> Gerd's latest patch depends on my not-yet-submitted patches, so just 
> simply drop this one. Gerd and I are going to coordinate this and 
> resubmit it again. Ok, Gerd?

I have a (temporary) #define for FE_(UN)REGISTER in there to relax the
dependencies between cx88 + dvb core a bit.  That way it is only a
runtime dependency and only for the dvb part of the cx88 driver.

Unfortunaly the #define catched only one of the two cases where it is
needed, and I didn't notice the second one as I'm working with a
dvb-patched kernel to actually test the stuff ...

Whats your planned timeframe for submitting the dvb updates?  I'd love
to see a working cx88 dvb driver in 2.6.9.

  Gerd

-- 
return -ENOSIG;

      reply	other threads:[~2004-09-17  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040916094323.GA11601@bytesex>
2004-09-16 23:08 ` [patch] v4l/dvb: cx88 driver update Andrew Morton
2004-09-17  6:37   ` Michael Hunold
2004-09-17  8:23     ` Gerd Knorr [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=20040917082347.GB16344@bytesex \
    --to=kraxel@bytesex.org \
    --cc=akpm@osdl.org \
    --cc=hunold@linuxtv.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