From: Michal Simek <monstr@monstr.eu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] microblaze: Fix level/edge irq sensibility
Date: Wed, 30 Mar 2011 14:05:44 +0200 [thread overview]
Message-ID: <4D931C98.4010009@monstr.eu> (raw)
In-Reply-To: <alpine.LFD.2.00.1103301403290.22418@localhost6.localdomain6>
Thomas Gleixner wrote:
> On Wed, 30 Mar 2011, Michal Simek wrote:
>
>> Patches:
>> "microblaze: Convert to new irq function names"
>> sha (4adc192ec7d977c74c750320f289af9d61c1caca)
>> and
>> "microblaze: Use generic show_interrupts()"
>> sha(9d61c18b25726306c9231428c17db42e3ff29ba7)
>>
>> should also setup edge/level in irq_set_chip_and_handler_name
>> name parameter.
>>
>> Error log:
>> ~ # cat /proc/interrupts
>> CPU0
>> 2: 2 Xilinx INTC-Xilinx INTC eth0
>> 3: 2 Xilinx INTC-Xilinx INTC eth0
>> 4: 241 Xilinx INTC-Xilinx INTC timer
>> 6: 108 Xilinx INTC-Xilinx INTC serial
>>
>> Fixed:
>> ~ # cat /proc/interrupts
>> CPU0
>> 2: 2 Xilinx INTC-level eth0
>> 3: 2 Xilinx INTC-level eth0
>> 4: 238 Xilinx INTC-edge timer
>> 6: 108 Xilinx INTC-level serial
>>
>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>
> Should I pick that up for the urgent fixes ?
No you shouldn't. It can go through my tree.
You can give me ACK if you like.
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-03-30 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 11:24 [PATCH v2] microblaze: Fix level/edge irq sensibility Michal Simek
2011-03-30 12:03 ` Thomas Gleixner
2011-03-30 12:05 ` Michal Simek [this message]
2011-03-30 12:08 ` Thomas Gleixner
2011-03-30 12:08 ` Michal Simek
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=4D931C98.4010009@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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