From: Andreas Engel <andreas.engel@marconi.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: [PATCH] cleanup duplicated ARM interrupt code
Date: Wed, 24 May 2006 14:14:15 +0200 [thread overview]
Message-ID: <44744E17.80701@marconi.com> (raw)
In-Reply-To: <20051121093754.00003629@idefix>
Hi,
please drop my patch from 21.11.2005. It doesn't work with the current
git head. Attached is an updated patch.
Regards,
Andreas Engel
CHANGELOG:
Clean up duplicated code: moved common ARM interrupt handling code
from cpu specific interrupts.c files into lib_arm/interrupts.c.
Patch by Andreas Engel, 24 May 2005
Signed-off-by: Andreas Engel
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diffstat.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20060524/5812489c/attachment.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: arm-irq.diff.gz
Type: application/x-gzip
Size: 4796 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060524/5812489c/attachment.bin
prev parent reply other threads:[~2006-05-24 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 8:37 [U-Boot-Users] [PATCH] cleanup duplicated ARM interrupt code Andreas Engel
2006-05-24 12:14 ` Andreas Engel [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=44744E17.80701@marconi.com \
--to=andreas.engel@marconi.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