From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Rewrite the MAJOR() macro as a call to imajor().
Date: Fri, 4 May 2007 04:14:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705040410390.20834@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0705041008180.18504@yvahk01.tjqt.qr>
On Fri, 4 May 2007, Jan Engelhardt wrote:
>
> On May 3 2007 23:18, Andrew Morton wrote:
> >> struct inode *i = file->f_mapping->host;
> >>
> >> - return i && S_ISBLK(i->i_mode) && MAJOR(i->i_rdev) == LOOP_MAJOR;
> >> + return i && S_ISBLK(i->i_mode) && imajor(i) == LOOP_MAJOR;
> >> }
> >
> >there's no runtime change, and I count a couple hundred MAJORs in the tree.
>
> Why do we even have imajor() if all it does is calling the MAJOR()
> macro?
i'm guessing it's to hide the underlying implementation of
extracting the major/minor numbers from an inode, in case that
implementation ever changes, which strikes me as perfectly reasonable.
and i don't think you'd have any luck arguing that it should be
removed at this point:
$ grep -Erw "(imajor|iminor)" * | wc -l
350
all i was doing was standardizing the small handful of holdouts.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-04 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 10:23 Robert P. J. Day
2007-05-04 6:18 ` Andrew Morton
2007-05-04 7:20 ` Robert P. J. Day
2007-05-04 8:09 ` Jan Engelhardt
2007-05-04 8:14 ` Robert P. J. Day [this message]
2007-05-04 11:42 ` Jan Engelhardt
2007-05-04 12:21 ` Robert P. J. Day
2007-05-04 12:34 ` Jan Engelhardt
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=Pine.LNX.4.64.0705040410390.20834@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=akpm@linux-foundation.org \
--cc=jengelh@linux01.gwdg.de \
--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
all inboxes | Powered by JetHome®