All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 2/7] sparc32,leon: add support for extended interrupt
Date: Wed, 20 Apr 2011 06:40:28 +0000	[thread overview]
Message-ID: <4DAE7FDC.6070109@gaisler.com> (raw)
In-Reply-To: <1303229239-21551-2-git-send-email-daniel@gaisler.com>

Sam Ravnborg wrote:

>Hi Daniel.
>
>A few nits that I missed during the private review.
>
>  
>
>>+#define LEON_IMASK (&leon3_irqctrl_regs->mask[0])
>>+#define LEON_IACK (&leon3_irqctrl_regs->iclear)
>>    
>>
>
>Hiding these behind macros may not make code more obvious.
>But I am not strongly about it.
>  
>
LEON_MASK was defined since before, I only removed a pair of unused 
parenteses and added LEON_IACK in the same spirit. I will leave it the 
way it is, I think it can be cleaned up later.

>  
>
>>+#define LEON_DO_ACK_HW 1
>> 
>>-/* Return the IRQ of the pending IRQ on the extended IRQ controller */
>>-int sparc_leon_eirq_get(int eirq, int cpu)
>>+/* Return the last ACKed IRQ by the Extended IRQ controller. It has already
>>+ * been (automatically) ACKed when the CPU takes the trap.
>>+ */
>>    
>>
>In general - nice to see the improved comments
>
>  
>
>> /* The extended IRQ controller has been found, this function registers it */
>>-void sparc_leon_eirq_register(int eirq)
>>+void leon_eirq_setup(unsigned int eirq)
>> {
>>-	int irq;
>>+	unsigned long mask, oldmask;
>>+	int veirq;
>>    
>>
>
>veirq is used for an unsigned int value later.
>Use "unsigned int" to avoid mixing signed/unsigned.
>  
>
I will fix this and resend the patch.

Thanks,
Daniel

      parent reply	other threads:[~2011-04-20  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 16:07 [PATCH 2/7] sparc32,leon: add support for extended interrupt controller Daniel Hellstrom
2011-04-19 18:34 ` [PATCH 2/7] sparc32,leon: add support for extended interrupt Sam Ravnborg
2011-04-20  6:40 ` Daniel Hellstrom [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=4DAE7FDC.6070109@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.