All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anisse Astier <anisse@astier.eu>
To: Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
	Matthew Wilcox <matthew.r.wilcox@intel.com>,
	linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [BUG] NVMe: compilation error
Date: Wed, 8 Feb 2012 11:22:10 +0100	[thread overview]
Message-ID: <20120208112210.10f41e68@destiny.ordissimo> (raw)
In-Reply-To: <20120203142536.GL12978@smp.if.uj.edu.pl>

On Fri, 3 Feb 2012 15:25:36 +0100, Witold Baryluk <baryluk@smp.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

      reply	other threads:[~2012-02-08 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 14:25 [BUG] NVMe: compilation error Witold Baryluk
2012-02-08 10:22 ` Anisse Astier [this message]

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=20120208112210.10f41e68@destiny.ordissimo \
    --to=anisse@astier.eu \
    --cc=baryluk@smp.if.uj.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.r.wilcox@intel.com \
    --cc=torvalds@linux-foundation.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.