public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 08/13] SPARC: added SMC91111 driver in and out macros for LEON processors.
Date: Mon, 31 Mar 2008 10:53:12 -0400	[thread overview]
Message-ID: <47F0FAD8.1080207@gmail.com> (raw)
In-Reply-To: <47F0F7EF.70609@gaisler.com>

Daniel Hellstrom wrote:
> Ben Warren wrote:
>
>> Daniel Hellstrom wrote:
>>
>>> Ben Warren wrote:
>>>  
>>>
>>>> I haven't looked at how all the funky macros in this patch are 
>>>> called, but it's generally considered good form to wrap multi-line 
>>>> macros with do {...} while(0) in order to avoid compiler issues. 
>>>> I'll NAK the patch for now based on this.
>>>>     
>>>
>>>
>>> The Macros are used to read/write 8-,16-,32-bit words from the I/O 
>>> bus where the SMC MAC is. LEON2/3 is bigendian, so the macros swaps 
>>> the read and written data as well. The I/O bus is
>>> non-cacheable so no force cache miss is needed here.
>>>
>>> I have made the do{}while(0) you asked for and updated patch 8 and 
>>> my repository:
>>>
>>>
>>>   
>>
>> Per the e-mail by A. Rubini, I guess this isn't necessary.  Sorry for 
>> causing extra work for you.  I'll pull this into the net tree today.
>>
>> regards,
>> Ben
>
> I agree with you both. However, some of the macros should not be 
> "expression statements" as they return nothing this is also indicated 
> by the inline function declared in drivers/net/smc91111.c:
> static inline word SMC_inw(dword offset);
> static inline void SMC_outw(word value, dword offset);
> static inline byte SMC_inb(dword offset);
> static inline void SMC_outb(byte value, dword offset);
> static inline void SMC_insw(dword offset, volatile uchar* buf, dword 
> len);
> static inline void SMC_outsw(dword offset, uchar* buf, dword len);
>
> I my last patch I let the only the "true" "expressions statements" 
> have the gcc slang Alessandro speak of.
>
> I would prefer the last patch I sent, currently in the repository.
>
Very good.  Thanks for being so thorough!  Much more interesting than 
quibbling about whitespace...

regards,
Ben

  reply	other threads:[~2008-03-31 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 14:25 [U-Boot-Users] [PATCH 08/13] SPARC: added SMC91111 driver in and out macros for LEON processors Daniel Hellstrom
2008-03-31 14:21 ` Ben Warren
2008-03-31 14:40   ` Daniel Hellstrom
2008-03-31 14:53     ` Ben Warren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-28 19:22 [U-Boot-Users] [PATCH 01/13] SPARC: Added generic support for SPARC architecture Daniel Hellstrom
2008-03-28 19:22 ` [U-Boot-Users] [PATCH 08/13] SPARC: added SMC91111 driver in and out macros for LEON processors Daniel Hellstrom
2008-03-30  4:29   ` Ben Warren
     [not found]   ` <20080331111242.GA29923@mail.gnudd.com>
2008-03-31 14:15     ` Ben Warren

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=47F0FAD8.1080207@gmail.com \
    --to=biggerbadderben@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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