All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: piotr@hosowicz.com
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:18:13 +0200	[thread overview]
Message-ID: <201008171518.14032.arnd@arndb.de> (raw)
In-Reply-To: <4C6A8A73.1070003@example.com>

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"

> > 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.

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

	Arnd

  reply	other threads:[~2010-08-17 13:20 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 [this message]
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=201008171518.14032.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotr@hosowicz.com \
    --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.