[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120208112210.10f41e68@destiny.ordissimo>
Date: Wed, 8 Feb 2012 11:22:10 +0100
From: Anisse Astier <anisse@...ier.eu>
To: Witold Baryluk <baryluk@....if.uj.edu.pl>,
Matthew Wilcox <matthew.r.wilcox@...el.com>,
linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [BUG] NVMe: compilation error
On Fri, 3 Feb 2012 15:25:36 +0100, Witold Baryluk <baryluk@....if.uj.edu.pl> wrote :
> Hi,
>
> when doing compiling I got
>
> CC [M] drivers/block/nvme.o
> drivers/block/nvme.c: In function ‘nvme_configure_admin_queue’:
> drivers/block/nvme.c:999:2: error: implicit declaration of function ‘writeq’ [-Werror=implicit-function-declaration]
> drivers/block/nvme.c:1003:2: error: implicit declaration of function ‘readq’ [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
I'm having the same problem, my build is broken(3.3-rc2+), and I don't
use -Werror (gcc (Debian 4.4.5-8) 4.4.5):
CC [M] drivers/block/nvme.o
drivers/block/nvme.c: In function ‘nvme_configure_admin_queue’:
drivers/block/nvme.c:999: error: implicit declaration of function ‘writeq’
drivers/block/nvme.c:1003: error: implicit declaration of function ‘readq’
>From a quick look at the code, writeq/readq are only defined for 64bits
builds, everywhere else it keeps being redefined (static definitons).
Regards,
Anisse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists