From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [PATCH 3/3] Final removal of FASTCALL()/fastcall
Date: Mon, 11 Feb 2008 13:26:44 -0800 [thread overview]
Message-ID: <1202765204.10004.18.camel@brick> (raw)
In-Reply-To: <20080211131738.dda66683.akpm@linux-foundation.org>
On Mon, 2008-02-11 at 13:17 -0800, Andrew Morton wrote:
> On Mon, 11 Feb 2008 10:38:42 -0800
> Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > All users are gone, remove definitions and comments referring
> > to them.
>
> I'm still showing occurrences in:
>
> ./Documentation/RCU/NMI-RCU.txt
> ./Documentation/kprobes.txt
> ./Documentation/uml/UserModeLinux-HOWTO.txt
> ./kernel/rcupdate.c
>
> The last one is interesting:
>
> /* FASTCALL no longer exists, this wrapper may no longer be needed */
> static void wakeme_after_rcu(struct rcu_head *head)
> {
> struct rcu_synchronize *rcu;
>
> rcu = container_of(head, struct rcu_synchronize, head);
> complete(&rcu->completion);
> }
>
> The comment is rather ungrammatical/meaningless. Perhaps it is trying
> to tell us that we can remove this function now?
Sorry, I added that as a note in my patch to look into and ended up
forgetting about it.
The original comment that was there read:
/* Because of FASTCALL declaration of complete, we use this wrapper */
Sorry about that, I'll look into the last occurances and send you a
patch 4/3.
Harvey
next prev parent reply other threads:[~2008-02-11 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 18:38 [PATCH 3/3] Final removal of FASTCALL()/fastcall Harvey Harrison
2008-02-11 21:17 ` Andrew Morton
2008-02-11 21:26 ` Harvey Harrison [this message]
2008-02-11 21:45 ` [PATCH 4/3] Documentation: Remove references to FASTCALL/fastcall Harvey Harrison
2008-02-12 1:49 ` [PATCH 3/3] Final removal of FASTCALL()/fastcall Paul E. McKenney
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=1202765204.10004.18.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
/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.