public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "\"Frédéric Weisbecker\"" <fweisbec@gmail.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: linux-next: build failure after merge of the bkl-ioctl tree
Date: Thu, 29 Apr 2010 22:40:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1004292239320.8472@localhost.localdomain> (raw)
In-Reply-To: <20100429154947.fbacee1f.sfr@canb.auug.org.au>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1732 bytes --]



On Thu, 29 Apr 2010, Stephen Rothwell wrote:

> Hi Frédéric,
> 
> After merging the bkl-ioctl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/scsi/3w-xxxx.c: In function 'tw_chrdev_ioctl':
> drivers/scsi/3w-xxxx.c:896: error: 'inode' undeclared (first use in this function)
> 
> Caused by commit 5c9af160f830a68734f600fc0f90cba35e26727b ("scsi: Push
> down BKL into ioctl functions").
> 
> I have used the version of the blk-ioctl tree from next-20100428 for
> today.

Frederic: did you miss one of my patches to fix the scsi compile problems?

The following should have fixed the above:

>From 3605ca2d1b29511fe1c95b47c4c596f392797585 Mon Sep 17 00:00:00 2001
From: John Kacur <jkacur@redhat.com>
Date: Tue, 27 Apr 2010 10:47:43 +0200
Subject: [PATCH 04/10] bkl: Fix missing inode tw_chrdev_ioctl due to bkl pushdown
Cc: Arnd Bergmann <arnd@arndb.de>,
    Linus Torvalds <torvalds@linux-foundation.org>,
    Frederic Weisbecker <fweisbec@gmail.com>,
    Jan Blunck <jblunck@gmail.com>,
    Thomas Gleixner <tglx@linutronix.de>

Signed-off-by: John Kacur <jkacur@redhat.com>
---
 drivers/scsi/3w-xxxx.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/scsi/3w-xxxx.c b/drivers/scsi/3w-xxxx.c
index 45a737c..2957691 100644
--- a/drivers/scsi/3w-xxxx.c
+++ b/drivers/scsi/3w-xxxx.c
@@ -890,6 +890,7 @@ static long tw_chrdev_ioctl(struct file *file, unsigned int cmd, unsigned long a
 	unsigned long data_buffer_length_adjusted = 0;
 	unsigned long *cpu_addr;
 	long timeout;
+	struct inode *inode = file->f_dentry->d_inode;
 	TW_New_Ioctl *tw_ioctl;
 	TW_Passthru *passthru;
 	TW_Device_Extension *tw_dev = tw_device_extension_list[iminor(inode)];
-- 
1.6.6.1

  reply	other threads:[~2010-04-30 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  5:49 linux-next: build failure after merge of the bkl-ioctl tree Stephen Rothwell
2010-04-29 20:40 ` John Kacur [this message]
2010-04-29 20:50   ` Frederic Weisbecker

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=alpine.LFD.2.00.1004292239320.8472@localhost.localdomain \
    --to=jkacur@redhat.com \
    --cc=arnd@arndb.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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