public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: ioctl definition - has it changed recently?
Date: Tue, 17 Aug 2010 15:51:32 +0200	[thread overview]
Message-ID: <4C6A93E4.8000500@example.com> (raw)
In-Reply-To: <201008171518.14032.arnd@arndb.de>

On 17.08.2010 15:18, Arnd Bergmann wrote:
> On Tuesday 17 August 2010, Piotr Hosowicz wrote:
>>>> Just take a look at all the other patches that went into the
>>>> kernel to do this for other drivers.
>>
>> I do not know how to find them. :-(
>
> git log -p -S"unlocked_ioctl"

Thanks a lot.

>>> It seems different. How to change it? Now it works, I built it without
>>> your remarks, exactly how I described on my blog:
>>>
>>> http://phosowicz.jogger.pl/2010/08/15/nvidia-graphics-in-fresh-kernels/
>>
>> Ok, as I wrote the prototypes differ. What should I do with the inode
>> parameter?
>
> It's normally not needed.

It seems so because the implementation nowwhere refers to the inode 
parameter. But I guess it won't be OK to just remove this parameter from 
the declaraion and the implemetation because some other NVidia code may 
refer to this parameter, pass it and so on. Potentially scrambling 
(spoiling) the parameter stack.

Regards,

Piotr Hosowicz

> If you do need it, use file->f_path.dentry->d_inode.

Ok, as I said - it is nowhere used. So this is not a problem.

Regards,

Piotr Hosowicz

-- 
Na przyjęciu chłopak pyta blondynkę:
- Czy mogę cię prosić do walca?
- Zgłupiałeś? To już nie miałeś czym przyjechać?
NP:  -
NB: 2.6.36-rc1

  reply	other threads:[~2010-08-17 13:51 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
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 [this message]
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=4C6A93E4.8000500@example.com \
    --to=piotr@hosowicz.com \
    --cc=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox