From: Andrew Morton <akpm@osdl.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: torvalds@osdl.org, dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1)
Date: Mon, 12 Jul 2004 11:11:20 -0700 [thread overview]
Message-ID: <20040712111120.2094f089.akpm@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0407121519380.17199@waterleaf.sonytel.be>
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Sun, 11 Jul 2004, Linus Torvalds wrote:
> > David Howells:
> > o kAFS automount support
>
> After this change, all archs need to provide struct_cpy() to make AFS compile,
> while currently only ia32 and amd64 provide it.
Seems a strange thing to do. Why not rely on the type system?
diff -puN fs/afs/mntpt.c~kafs-struct_cpy fs/afs/mntpt.c
--- 25/fs/afs/mntpt.c~kafs-struct_cpy 2004-07-12 11:08:39.125941824 -0700
+++ 25-akpm/fs/afs/mntpt.c 2004-07-12 11:08:55.972380776 -0700
@@ -250,7 +250,7 @@ static int afs_mntpt_follow_link(struct
if (IS_ERR(newmnt))
return PTR_ERR(newmnt);
- struct_cpy(&newnd, nd);
+ newnd = *nd;
newnd.dentry = dentry;
err = do_add_mount(newmnt, &newnd, 0, &afs_vfsmounts);
diff -puN fs/afs/vlocation.c~kafs-struct_cpy fs/afs/vlocation.c
--- 25/fs/afs/vlocation.c~kafs-struct_cpy 2004-07-12 11:08:39.141939392 -0700
+++ 25-akpm/fs/afs/vlocation.c 2004-07-12 11:09:31.815931728 -0700
@@ -906,7 +906,7 @@ static cachefs_match_val_t afs_vlocation
if (!vlocation->valid ||
vlocation->vldb.rtime == vldb->rtime
) {
- struct_cpy(&vlocation->vldb, vldb);
+ vlocation->vldb = *vldb;
vlocation->valid = 1;
_leave(" = SUCCESS [c->m]");
return CACHEFS_MATCH_SUCCESS;
@@ -947,7 +947,7 @@ static void afs_vlocation_cache_update(v
_enter("");
- struct_cpy(vldb,&vlocation->vldb);
+ *vldb = vlocation->vldb;
} /* end afs_vlocation_cache_update() */
#endif
_
next prev parent reply other threads:[~2004-07-12 18:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 18:29 Linux 2.6.8-rc1 Linus Torvalds
2004-07-11 23:00 ` [PATCH] edd (Re: Linux 2.6.8-rc1) Randy.Dunlap
2004-07-12 3:02 ` Adrian Bunk
2004-07-12 4:49 ` Matt Domsch
2004-07-12 5:21 ` Randy.Dunlap
2004-07-12 9:26 ` Linux 2.6.8-rc1 Matthias Andree
2004-07-12 18:54 ` Martin Schlemmer
2004-07-12 9:34 ` Paolo Ciarrocchi
2004-07-12 15:42 ` Adrian Bunk
2004-07-12 15:56 ` Paolo Ciarrocchi
2004-07-12 16:34 ` Adrian Bunk
2004-07-12 16:43 ` Linus Torvalds
2004-07-12 20:28 ` Paolo Ciarrocchi
2004-07-12 20:22 ` Paolo Ciarrocchi
2004-07-13 20:54 ` cliff white
2004-07-12 21:08 ` Horst von Brand
2004-07-12 11:30 ` is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 13:51 ` Andy Whitcroft
2004-07-12 14:23 ` Geert Uytterhoeven
2004-07-12 12:01 ` Linux 2.6.8-rc1 Geert Uytterhoeven
2004-07-12 13:18 ` OGAWA Hirofumi
2004-07-12 13:25 ` Geert Uytterhoeven
2004-07-12 14:02 ` OGAWA Hirofumi
2004-07-12 13:23 ` struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 18:11 ` Andrew Morton [this message]
2004-07-12 18:23 ` Christoph Hellwig
2004-07-12 18:40 ` Andrew Morton
2004-07-13 10:14 ` David Howells
2004-07-12 23:49 ` Linux 2.6.8-rc1 (compile stats) John Cherry
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=20040712111120.2094f089.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®