linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] sata_mv Improve naming of main_irq cause/mask identifiers
Date: Tue, 29 Apr 2008 02:18:36 -0400	[thread overview]
Message-ID: <4816BDBC.3000804@pobox.com> (raw)
In-Reply-To: <4811F7A8.6080004@rtr.ca>

Mark Lord wrote:
> Jeff Garzik wrote:
> ..
>> applied patches 1-8...
> ..
>>> -    irq_stat = readl(hpriv->main_cause_reg_addr);
>>> -    irq_mask = readl(hpriv->main_mask_reg_addr);
> ..
>>> +    main_cause = readl(hpriv->main_cause_reg_addr);
>>> +    main_mask  = readl(hpriv->main_mask_reg_addr);
> ..
>>  ...but I am sad to see this.  irq_stat and irq_mask naming make the 
>> driver more accessible to outsiders, because the purpose of the 
>> registers is immediately apparent even without having the docs at hand 
>> -- which is the case for everybody in the world except me and you :)
>>
>> I applied the patch anyway because you are defacto maintainer of sata_mv.
>>
>> However, I _request_ a reconsideration of some of these renames when 
>> viewed in that light.  It's your prerogative as maintainer to ignore 
>> or honor that request as you see fit...  We all have to balance making 
>> our own job easier with making the driver accessible to outsiders, 
>> particularly those without NDA'd docs.
> ..
> 
> Here ya go:
> 
> -------------------- SNIP ----------------------------------
> 
> Tidy up naming of things associated with the PCI / SOC chip
> "main irq cause/mask" registers, as inspired by Jeff.
> 
> Signed-off-by: Mark Lord <mlord@pobox.com>

applied



      reply	other threads:[~2008-04-29  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 15:24 [PATCH] sata_mv Improve naming of main_irq cause/mask identifiers Mark Lord
2008-04-29  6:18 ` Jeff Garzik [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=4816BDBC.3000804@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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).