linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 13/15] ide: add ata_set{_max}_pio()
Date: Sat, 30 Jun 2007 16:21:05 -0400	[thread overview]
Message-ID: <4686BB31.7040205@garzik.org> (raw)
In-Reply-To: <200706302231.10032.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> This has been changing recently since "ide_" prefix seems to have
> negative emotional connotations. :-)
> 
> New patches for drivers/ide should use exclusively the "ata_" prefix.

So this choice to be inconsistent was made based entirely on fashion?

This is the same as using a different coding style in one area of the 
IDE driver, when the rest of the IDE driver uses another coding style.

It violates the Principle of Least Surprise.

I cannot see any harm in continuing to use the prefix the IDE driver has 
been using for over a decade, while I can see how inconsistency


>> particularly when libata uses the "ata_" prefix almost exclusively.
> 
> I don't see *any* problem with this since libata exists in the separate
> directory and the amount of code shared between libata and drivers/ide
> equals *zero* (not counting <linux/ata.h> containing defines etc).

There are many opportunities for confusion:  global grep.  oops traces. 
  General reviewer expectations ("oooh, I grepped for ide_xxx because 
thats what all the functions use, except for this ONE function that's 
different")

You are living in a global namespace.  Directories are irrelevant.

	Jeff



  reply	other threads:[~2007-06-30 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 19:11 [PATCH 13/15] ide: add ata_set{_max}_pio() Bartlomiej Zolnierkiewicz
2007-06-30 20:03 ` Jeff Garzik
2007-06-30 20:31   ` Bartlomiej Zolnierkiewicz
2007-06-30 20:21     ` Jeff Garzik [this message]
2007-06-30 20:46       ` Bartlomiej Zolnierkiewicz
2007-06-30 22:39     ` Alan Cox

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=4686BB31.7040205@garzik.org \
    --to=jeff@garzik.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).