All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: torvalds@linux-foundation.org,
	Peter Senna Tschudin <peter.senna@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hlist: drop the node parameter from iterators
Date: Wed, 30 Jan 2013 15:47:25 -0800	[thread overview]
Message-ID: <20130130154725.f7b40daa.akpm@linux-foundation.org> (raw)
In-Reply-To: <5108728E.5020901@oracle.com>

On Tue, 29 Jan 2013 20:08:30 -0500
Sasha Levin <sasha.levin@oracle.com> wrote:

> Also, ping :)
>
> ...
>
> >  216 files changed, 1031 insertions(+), 1526 deletions(-)

Whimper.

I don't really see a sane way of avoiding a single huge atomic smash
here.  Normally we'd use a multistep process:

1: Create a new and differently named macro, say "sasha_is_a_pita()".

2: Convert hlist_for_each_entry() to sasha_is_a_pita() in as many
   sites as we can.

3: Once we think all sites are converted, delete the now-unused
   hlist_for_each_entry() definition.

Problem is, there just isn't any other identifier we can use here apart
from hlist_for_each_entry().

I suppose we could add additional steps:

4: Add hlist_for_each_entry(), which is identical to sasha_is_a_pita().

5: Convert sasha_is_a_pita() to hlist_for_each_entry() in as many
   sites as we can.

6: Once we think all sites are converted, delete the now-unused
   sasha_is_a_pita() definition.

But geeze.


The alternative is to do the huge atomic smash immediately after the
3.9-rc1 release, when the amount of pending out-of-tree code is at a
minimum.


  reply	other threads:[~2013-01-30 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1358998645-20452-1-git-send-email-sasha.levin@oracle.com>
2013-01-30  1:08 ` [PATCH] hlist: drop the node parameter from iterators Sasha Levin
2013-01-30 23:47   ` Andrew Morton [this message]
2013-01-31  0:09     ` Sasha Levin
2013-01-31  0:22       ` Andrew Morton
2013-01-31  0:55         ` Sasha Levin
2013-01-11 18:01 Sasha Levin
2013-01-11 22:19 ` Sasha Levin

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=20130130154725.f7b40daa.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    --cc=sasha.levin@oracle.com \
    --cc=torvalds@linux-foundation.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.