From: Linus Torvalds <torvalds@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [AF_RXRPC]: Make the in-kernel AFS filesystem use AF_RXRPC.
Date: Tue, 1 May 2007 09:23:08 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705010918550.3808@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705011734410.27246@anakin>
On Tue, 1 May 2007, Geert Uytterhoeven wrote:
>
> This causes a compile failure on m68k:
>
> | linux/fs/afs/fsclient.c: In function 'afs_deliver_fs_fetch_data':
> | linux/fs/afs/fsclient.c:269: warning: dereferencing 'void *' pointer
> | linux/fs/afs/fsclient.c:269: error: request for member 'virtual' in something not a structure or union
>
> Probably you wanted to assign call->reply3 to a struct page pointer first, like you do for the call->unmarshall == 2 case.
Hmm. Wouldn't it be nicer to make "kmap_atomic()" be an inline function
instead? That way, if you pass it a "void *", it still just works, and you
get a much nicer/more readable error message too when the types actually
don't match?
Of course, there may be some reason why <linux/highmem.h> does those with
#define's rather than inline functions. Maybe "page_address()" or
"pagefault_disabled()" is not declared at that point, and asking it to be
declared might cause header file inclusion recursion?
Linus
next prev parent reply other threads:[~2007-05-01 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704271707.l3RH7H5Z032671@hera.kernel.org>
2007-05-01 15:41 ` Geert Uytterhoeven
2007-05-01 16:23 ` Linus Torvalds [this message]
2007-05-01 17:51 ` Geert Uytterhoeven
2007-05-01 16:14 ` David Howells
2007-05-01 16:31 ` Geert Uytterhoeven
2007-05-01 16:58 ` David Howells
2007-05-01 17:52 ` Geert Uytterhoeven
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.0.98.0705010918550.3808@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®