linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 (mvista rsync) -- drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in something not a structure or union
Date: 10 Aug 2003 22:38:40 +0200	[thread overview]
Message-ID: <1060547919.599.34.camel@gaston> (raw)
In-Reply-To: <200308100851.04174.miles.lane@comcast.net>


On Sun, 2003-08-10 at 17:51, Miles Lane wrote:
>   CC      drivers/ide/ppc/pmac.o
> drivers/ide/ppc/pmac.c: In function `pmac_ide_build_sglist':
> drivers/ide/ppc/pmac.c:1198: warning: passing arg 1 of `blk_rq_map_sg' from
> incompatible pointer type
> drivers/ide/ppc/pmac.c: In function `pmac_ide_dma_test_irq':
> drivers/ide/ppc/pmac.c:1673: warning: comparison is always false due to
> limited range of data type
> drivers/ide/ppc/pmac.c: In function `idepmac_wake_device':
> drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in
> something not a structure or union
> drivers/ide/ppc/pmac.c: In function `idepmac_wake_drive':
> drivers/ide/ppc/pmac.c:1927: error: request for member `queue_head' in
> something not a structure or union

I sent an updated version of this driver to linus today

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-08-10 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 15:51 linuxppc-2.5 (mvista rsync) -- drivers/ide/ppc/pmac.c:1843: error: request for member `queue_head' in something not a structure or union Miles Lane
2003-08-10 15:57 ` Miles Lane
2003-08-10 20:38 ` Benjamin Herrenschmidt [this message]
2003-08-10 20:51   ` Miles Lane
2003-08-10 20:55     ` Benjamin Herrenschmidt

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=1060547919.599.34.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=miles.lane@comcast.net \
    /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;
as well as URLs for NNTP newsgroup(s).