mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Ian Campbell <icampbell@arcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: use datacs is smc91x driver
Date: Tue, 25 Jan 2005 10:41:45 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501251038030.16341@localhost.localdomain> (raw)
In-Reply-To: <1106665612.19123.142.camel@icampbell-debian>

On Tue, 25 Jan 2005, Ian Campbell wrote:

> On Tue, 2005-01-25 at 11:14 +0000, Ian Campbell wrote:
> > Are you happy with "iocs", "attrib" and "datacs" for the names?
> 
> Of the platforms with an smc91x platform_device (according to grep) only
> 2 (lubbock, neponset) out of the 18 have memory resources other than the
> iocs (full list of platforms is at the end, after the patch)
> 
> So for the sake of the least intrusive patch I think for the main iocs
> I'll call _byname and fallback on mem resource number 0 if no named iocs
> resource exists. attrib and datacs must be explicitly named. This allows
> most of the board ports to remain unchanged.

Sensible.

> I also noticed that the name propagates into /proc/iomem etc
> 	# cat /proc/iomem
> 	[...]
> 	10000000-10000003 : datacs
> 	  10000000-10000003 : smc91x
> so perhaps smc91x-datacs -attrib -iocs might be more appropriate names?

Probably, although "iocs" is rather criptic for someone not familiar 
with the chip.  What about "smc91x-regs", "smc91x-attrib" and 
"smc91x-data32" ?


Nicolas

  reply	other threads:[~2005-01-25 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 12:21 Ian Campbell
2005-01-24 20:20 ` Nicolas Pitre
2005-01-25 11:14   ` Ian Campbell
2005-01-25 15:06     ` Ian Campbell
2005-01-25 15:41       ` Nicolas Pitre [this message]
2005-01-25 16:24         ` Ian Campbell
2005-01-25 16:51           ` Nicolas Pitre
2005-01-25 17:05             ` [PATCH] " Ian Campbell

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.61.0501251038030.16341@localhost.localdomain \
    --to=nico@cam.org \
    --cc=icampbell@arcom.com \
    --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®