From: Jesper Juhl <jesper.juhl@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 1/7] rename locking functions - do the rename
Date: Thu, 18 Aug 2005 23:14:38 +0200 [thread overview]
Message-ID: <9a87484905081814145a58d160@mail.gmail.com> (raw)
In-Reply-To: <20050818110051.GA6606@infradead.org>
On 8/18/05, Christoph Hellwig <hch@infradead.org> wrote:
> On Thu, Aug 18, 2005 at 02:07:14AM +0200, Jesper Juhl wrote:
> > This patch renames sema_init to init_sema, init_MUTEX to init_mutex and
> > init_MUTEX_LOCKED to init_mutex_locked and at the same time creates 3
> > (deprecated) wrapper functions with the old names.
>
> What's the point? There's not need for totally gratious renaming.
>
I don't consider this "gratious renaming". I didn't do this just
because I could. I did it because the names used in the locking API
are quite inconsistent and not exactely pretty. I did it to make
things cleaner, neater, more consistent - to do everyone a favour.
Yes, it's just renaming of functions, it doesn't actually change any
behaviour, but why should we have to live with less-than-perfect
naming when we can clean it up?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2005-08-18 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 0:07 [PATCH 1/7] rename locking functions - do the rename Jesper Juhl
2005-08-18 11:00 ` Christoph Hellwig
2005-08-18 21:14 ` Jesper Juhl [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=9a87484905081814145a58d160@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.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