From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/7] sparc32,leon: additional genirq patches
Date: Wed, 20 Apr 2011 09:49:12 +0000 [thread overview]
Message-ID: <4DAEAC18.6080405@gaisler.com> (raw)
In-Reply-To: <4DADB2F4.6070402@gaisler.com>
David Miller wrote:
>From: Daniel Hellstrom <daniel@gaisler.com>
>Date: Tue, 19 Apr 2011 18:06:12 +0200
>
>
>
>>Hello Dave,
>>
>>All the changes in this patch set [1..7] must be applied on top
>>of Sam genirq patch. The are all LEON specific.
>>
>>They add:
>>* mask/unmask spinlock protection
>>* Support for LEON Extended IRQ controller
>>* Use new genirq layer for per-cpu Timer ISR (cleanup)
>>* other cleanups
>>* add support for CPU affinity
>>
>>Daniel Hellstrom
>>
>>
>
>Hey Daniel, could you please address Sam's feedback on a few patches
>and then resubmit this? You can integrate the ACK's he gave for
>some of the patches when you do that.
>
>
It became a bit more messy than my intension... I have added Sam's
boot_cpu_id patch in front of my patches, and previous patch 6 (now 7)
has been swapped with previous patch 7 (now 8). I have added Sam's ACK.
The previous patch 6 which I was supposed to drop have now been cleaned
up using Sam's boot_cpu_id instead of a LEON specific variable
leon3_boot_cpu.
Thanks,
Daniel
next prev parent reply other threads:[~2011-04-20 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 16:06 [PATCH 0/7] sparc32,leon: additional genirq patches Daniel Hellstrom
2011-04-20 5:42 ` David Miller
2011-04-20 9:49 ` Daniel Hellstrom [this message]
2011-04-20 11:23 ` Daniel Hellstrom
2011-04-20 12:58 ` Sam Ravnborg
2011-04-21 18:09 ` David Miller
2011-04-21 18:46 ` daniel
2011-04-21 22:31 ` David Miller
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=4DAEAC18.6080405@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.