From: Piotr Hosowicz <piotr@hosowicz.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: ioctl definition - has it changed recently?
Date: Sun, 15 Aug 2010 00:10:29 +0200 [thread overview]
Message-ID: <4C671455.4040908@example.com> (raw)
In-Reply-To: <20100814210044.GA29375@merkur.ravnborg.org>
On 14.08.2010 23:00, Sam Ravnborg wrote:
> On Sat, Aug 14, 2010 at 10:53:17PM +0200, Piotr Hosowicz wrote:
>> Hello,
>>
>> I build new kernels when they become available. Now I have a problem.
>> After I install new kernel I have to run NVidia setup script. Starting
>> from git15 it fails, see attached file. The error line is here:
>>
>> /tmp/selfgz6622/NVIDIA-Linux-x86_64-256.35/kernel/nv.c: At top level:
>> /tmp/selfgz6622/NVIDIA-Linux-x86_64-256.35/kernel/nv.c:426: error:
>> unknown field ‘ioctl’ specified in initializer
>> /tmp/selfgz6622/NVIDIA-Linux-x86_64-256.35/kernel/nv.c:426: warning:
>> initialization from incompatible pointer type
>
> The likely culprint is:
> b19dd42faf413b4705d4adb38521e82d73fa4249
> (bkl: Remove locked .ioctl file operation)
>
> This commit finally killed ioctl from file_operations, as part of the
> bkl removal project.
Yes, this was it. I made git pull and git revert and now I am up and
kicking. But how will I manage with it not by git but by kernel org
provioded files? And even if I used git all the time will I have to
revert it each time and what's the worse I will become more and more out
of sync because people will write their code as if I did not revert.
Thanks for your help. Regards,
Piotr Hosowicz
--
- Jaka jest największa anomalia fizjologiczno-polityczna?
- Członek wysunięty z ramienia na czoło.
NP: Peter Green Splinter Group - Big Change Is Gonna Come
NB: 2.6.35-20100814-2310+
next prev parent reply other threads:[~2010-08-14 22:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 20:53 ioctl definition - has it changed recently? Piotr Hosowicz
2010-08-14 21:00 ` Sam Ravnborg
2010-08-14 22:10 ` Piotr Hosowicz [this message]
2010-08-16 6:58 ` Arnd Bergmann
2010-08-16 7:11 ` Piotr Hosowicz
2010-08-16 7:17 ` Arnd Bergmann
2010-08-16 7:59 ` Piotr Hosowicz
2010-08-17 13:11 ` Piotr Hosowicz
2010-08-17 13:18 ` Arnd Bergmann
2010-08-17 13:51 ` Piotr Hosowicz
2010-08-17 13:59 ` Piotr Hosowicz
2010-08-17 14:33 ` Piotr Hosowicz
2010-08-14 21:02 ` Piotr Hosowicz
[not found] ` <20100814212007.GA26128@nuttenaction>
2010-08-15 8:24 ` Piotr Hosowicz
2010-08-15 11:57 ` Piotr Hosowicz
2010-08-15 14:22 ` Piotr Hosowicz
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=4C671455.4040908@example.com \
--to=piotr@hosowicz.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 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.