All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Schilling Landgraf <dougsland@gmail.com>
To: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
Cc: linux-media <linux-media@vger.kernel.org>,
	VDR User <user.vdr@gmail.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: V4L hg tree fails to compile against kernel 2.6.28
Date: Wed, 25 Aug 2010 01:21:29 -0400	[thread overview]
Message-ID: <AANLkTimwWj0sw0NKgaGBJmpKzjvwM1-U16+vToOg_Pyc@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinA1r87W+4J=MRV5i6M6BD-c+KTWnYqyBd7WCQA@mail.gmail.com>

Hi,

On Tue, Aug 24, 2010 at 11:45 PM, Douglas Schilling Landgraf
<dougsland@gmail.com> wrote:
> Hello Jan,
>
> On Tue, Aug 24, 2010 at 5:04 PM, Jan Hoogenraad
> <jan-conceptronic@hoogenraad.net> wrote:
>> Douglas:
>>
>> On compiling with  Linux  2.6.28-19-generic #62-Ubuntu
>>
>> I now get:
>>
>> dvb_demux.c: In function 'dvbdmx_write':
>> dvb_demux.c:1137: error: implicit declaration of function 'memdup_user'
>> dvb_demux.c:1137: warning: assignment makes pointer from integer without a
>> cast
>>
>> This is probably due to changeset 2ceef3d75547
>>
>> which introduced the use of this function:
>> http://linuxtv.org/hg/v4l-dvb/diff/2ceef3d75547/linux/drivers/media/dvb/dvb-core/dvb_demux.c
>>
>> This function is not available in linux/string.h in kernel 2.6.29 and lower.
>>
>> http://lxr.free-electrons.com/source/include/linux/string.h?v=2.6.28
>>
>> Could you please advise me on what to do ?
>
> For this issue, I have fixed right now, please try again with a
> updated repository. But since I have commited several patches
> yesterday,
> we have another one that probably will reach your compilantion (the
> kfifo one). I will work to fix this one too.
>
> Thanks for the report.


Ok, should be working right now, I have made the backports
needed/adjusts to compile agains 2.6.29. Let me know if you have any
problem.
Tomorrow I will continue commiting patches to get hg synced with git.

Thanks
Douglas

  reply	other threads:[~2010-08-25  5:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  6:36 V4L hg tree fails to compile against latest stable kernel 2.6.35 VDR User
2010-08-03  6:44 ` VDR User
     [not found]   ` <4C581BB6.7000303@redhat.com>
2010-08-05  5:19     ` Douglas Schilling Landgraf
2010-08-05  5:44       ` VDR User
2010-08-05 15:07         ` Douglas Schilling Landgraf
2010-08-14 16:46       ` VDR User
2010-08-15  5:22         ` Douglas Schilling Landgraf
2010-08-15 17:57           ` Douglas Schilling Landgraf
2010-08-15 18:50             ` VDR User
2010-08-24 20:04             ` V4L hg tree fails to compile against kernel 2.6.28 Jan Hoogenraad
2010-08-25  3:45               ` Douglas Schilling Landgraf
2010-08-25  5:21                 ` Douglas Schilling Landgraf [this message]
2010-08-25  6:26                 ` Jan Hoogenraad
2010-08-25 19:26                   ` Douglas Schilling Landgraf
2010-08-26  5:43                     ` Jan Hoogenraad
2010-08-26  6:53                       ` ir_codes_dibusb_table : please make table length a constant Jan Hoogenraad
2010-08-27  1:32                         ` 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=AANLkTimwWj0sw0NKgaGBJmpKzjvwM1-U16+vToOg_Pyc@mail.gmail.com \
    --to=dougsland@gmail.com \
    --cc=jan-conceptronic@hoogenraad.net \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=user.vdr@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.