public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Gefre <pfg@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, davidm@napali.hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Altix updates
Date: Tue, 20 Jan 2004 14:12:47 -0600	[thread overview]
Message-ID: <400D8BBF.7070005@sgi.com> (raw)
In-Reply-To: <20040120180851.A18872@infradead.org>

Christoph Hellwig wrote:

>On Tue, Jan 20, 2004 at 11:50:19AM -0600, Patrick Gefre wrote:
>  
>
>>Yes this probably looks a little odd. This was setup this way for TIO. 
>>The macro in the TIO code checks to see
>>if it is a 'soft' struct or bridge address AND what bridge type it is - 
>>accessing different registers depending
>>on TIO or not TIO (the 2 cases we have so far). We think this makes the 
>>register access functions pretty flexible/generic.
>>    
>>
>
>Sorry, but this is completly bogus.  Just declare one accessor per
>datatype.
>  
>

Guess I don't understand your point. Do you want us to create separate 
functions for soft-struct and bridge address
and TIO and non-TIO - 4 functions for each register access, rather than 1 ?

That seems to add a lot of extra code now and we'll need to add new 
functions as we add more ASIC interfaces - which is exactly
what we are trying to avoid. The way we have it, if we add a new ASIC we 
just need to make the lowest level functions ASIC-aware
and then we are done - no need to have blocks of if-then-else code in 
the mainline to determine which function to call.



  reply	other threads:[~2004-01-20 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 21:54 [PATCH 2.6] Altix updates Pat Gefre
2004-01-16  2:34 ` Andrew Morton
2004-01-16 14:41 ` Christoph Hellwig
2004-01-20 17:50   ` Patrick Gefre
2004-01-20 18:08     ` Christoph Hellwig
2004-01-20 20:12       ` Patrick Gefre [this message]
2004-01-20 20:21         ` Christoph Hellwig
2004-01-20 22:23           ` Patrick Gefre
2004-01-20 23:34             ` Christoph Hellwig
2004-01-21  0:23               ` Patrick Gefre
2004-01-21  0:26                 ` Christoph Hellwig

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=400D8BBF.7070005@sgi.com \
    --to=pfg@sgi.com \
    --cc=akpm@osdl.org \
    --cc=davidm@napali.hpl.hp.com \
    --cc=hch@infradead.org \
    --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