From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 1/8] sata_mv more cosmetics
Date: Fri, 25 Apr 2008 09:46:31 -0400 [thread overview]
Message-ID: <4811E0B7.2060508@rtr.ca> (raw)
In-Reply-To: <481168E7.50402@pobox.com>
Jeff Garzik wrote:
> Mark Lord wrote:
..
>> - 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.
..
Thanks, Jeff.
I agree, too, in principle if not in deed at the moment.
But there are just *so many* irq cause / mask registers in these chips,
(one for PCI, one for the host function, and one per-port for EDMA,
plus the SATA SError + mask, ..), that even I was getting confused
while working on the code.
So, for now, they've been renamed back to something closer to
what is used in the (NDA only) documentation.
I did consider main_irq_{cause,mask} as an even better set of names there,
but in the end went for the shortened versions to avoid hitting the
pedantic 80-character line "limits" too often.
Perhaps after we finish the major hacking around the interrupt/EH code
(yes, more to come..) we can try and fix up those names again.
I'll put it on the next TODO list update.
Cheers
next prev parent reply other threads:[~2008-04-25 13:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:42 [PATCH 0/8] sata_mv interrupt/eh fixes etc Mark Lord
2008-04-19 18:43 ` [PATCH 1/8] sata_mv more cosmetics Mark Lord
2008-04-25 5:15 ` Jeff Garzik
2008-04-25 13:46 ` Mark Lord [this message]
2008-04-25 16:40 ` Grant Grundler
2008-04-25 16:57 ` Jeff Garzik
2008-04-25 17:35 ` Mark Lord
2008-04-25 17:39 ` Grant Grundler
2008-04-25 17:31 ` Mark Lord
2008-04-19 18:44 ` [PATCH 2/8] sata_mv mask all interrupt coalescing bits Mark Lord
2008-04-19 18:45 ` [PATCH 3/8] sata_mv simplify freeze/thaw bit-shift calculations Mark Lord
2008-04-19 19:05 ` REPOST: " Mark Lord
2008-04-19 18:46 ` [PATCH 4/8] sata_mv simplify request/response queue handling Mark Lord
2008-04-19 19:06 ` REPOST: " Mark Lord
2008-04-19 18:52 ` [PATCH 5/8] sata_mv tidy host controller interrupt handling Mark Lord
2008-04-19 19:07 ` REPOST: " Mark Lord
2008-04-19 18:53 ` [PATCH 6/8] sata_mv more interrupt handling rework Mark Lord
2008-04-19 18:53 ` [PATCH 7/8] sata_mv leave SError bits untouched in mv_err_intr Mark Lord
2008-04-19 19:07 ` REPOST: " Mark Lord
2008-04-19 18:54 ` [PATCH 8/8] sata_mv re-enable hotplug, update TODO list Mark Lord
2008-04-19 19:09 ` Mark Lord
2008-04-23 13:32 ` [PATCH 0/8] sata_mv interrupt/eh fixes etc Mark Lord
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=4811E0B7.2060508@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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).