From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-main <linux-kernel@vger.kernel.org>,
linuxsh <linuxsh-dev@lists.sourceforge.net>
Subject: Re: [SUPERH] dma-mapping.h structure has no member named page
Date: Wed, 24 Oct 2007 16:34:42 -0700 [thread overview]
Message-ID: <20071024163442.1e3e6998.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <20071023230507.GP14671@kernel.dk>
On Wed, 24 Oct 2007 01:05:07 +0200
Jens Axboe <jens.axboe@oracle.com> wrote:
> On Tue, Oct 23 2007, Kristoffer Ericson wrote:
> > Greetings,
> >
> > Got this after syncing my tree with linux-2.6.git.
> >
> > In file included from include/linux/dma-mapping.h:52,
> > from include/linux/dmaengine.h:29,
> > from include/linux/skbuff.h:29,
> > from include/linux/netlink.h:155,
> > from include/linux/genetlink.h:4,
> > from include/net/genetlink.h:4,
> > from include/linux/taskstats_kern.h:12,
> > from init/main.c:46:
> > include/asm/dma-mapping.h: In function `dma_map_sg':
> > include/asm/dma-mapping.h:88: error: structure has no member named `page'
> > include/asm/dma-mapping.h:91: error: structure has no member named `page'
> > include/asm/dma-mapping.h: In function `dma_sync_sg':
> > include/asm/dma-mapping.h:141: error: structure has no member named `page'
> > include/asm/dma-mapping.h:144: error: structure has no member named `page'
> > make[1]: *** [init/main.o] Error 1
> > make: *** [init] Error 2
>
> Pull again, should be ok now.
Yeah, saw the posts on it last night. Everything worked fine after pulling again last night. Thx
>
> --
> Jens Axboe
>
prev parent reply other threads:[~2007-10-24 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 1:53 Kristoffer Ericson
2007-10-23 23:05 ` Jens Axboe
2007-10-24 23:34 ` Kristoffer Ericson [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=20071024163442.1e3e6998.Kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.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
Powered by JetHome