All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] misc: Removal of final callers using fastcall
Date: Thu, 20 Dec 2007 22:27:02 -0800	[thread overview]
Message-ID: <1198218422.8584.1.camel@brick> (raw)
In-Reply-To: <20071220183029.86ac61e4.akpm@linux-foundation.org>

On Thu, 2007-12-20 at 18:30 -0800, Andrew Morton wrote:
> On Wed, 12 Dec 2007 15:38:26 -0800 Harvey Harrison <harvey.harrison@gmail.com> wrote:
> 
> > Andrew, I'm not sure who is best to hit with these final dribs and
> > drabs removing fastcall.  Once all of these have hit Linus' tree
> > I will send a final patch deleting the include/linux/linkage.h
> > definitions as well as any remaining occurances.
> 
> Yes, that's a good approach, thanks.  Wait until the tree is fastcall-clean
> and then kill the definition(s).
> 
> I think I skipped rather a lot of remove-fastcall patches because a)
> suitable maintainers were cc'ed and b) I was going through a
> suicidal-over-bug-reports phase.
> 
> Please keep them coming - I've always disliked fastcall.

Once I see these have hit the main tree, I'll send patch getting any
more that have snuck in for the next rc.  After that there should be
few enough left that I can send you a small patch for the next rc
with the definition removal as well.

I'll keep on top of these.

Harvey




      reply	other threads:[~2007-12-21  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 23:38 [PATCH] misc: Removal of final callers using fastcall Harvey Harrison
2007-12-21  2:30 ` Andrew Morton
2007-12-21  6:27   ` Harvey Harrison [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=1198218422.8584.1.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --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 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.