From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: Wolfgang Ocker <weo@reccoware.de>
Subject: Re: [PATCH] PPC440EP Interrupt Triggering and Level Settings
Date: Mon, 11 Feb 2008 07:33:56 +0100 [thread overview]
Message-ID: <200802110733.57267.sr@denx.de> (raw)
In-Reply-To: <1202671442.3384.15.camel@galileo.recco.de>
On Sunday 10 February 2008, Wolfgang Ocker wrote:
> From: Wolfgang Ocker <weo@reccoware.de>
>
> Corrected IRQ triggering and level settings according to latest revision
> of the 440EP User Manual (rev 1.24 nov 16, 2007).
>
> The incorrect settings might cause a failure of the network if both
> onchip ethernet ports are under heavy load.
>
> Signed-off-by: Wolfgang Ocker <weo@reccoware.de>
Thanks, looks good.
Acked-by: Stefan Roese <sr@denx.de>
Best regards,
Stefan
next prev parent reply other threads:[~2008-02-11 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 19:24 [PATCH] PPC440EP Interrupt Triggering and Level Settings Wolfgang Ocker
2008-02-11 6:33 ` Stefan Roese [this message]
2008-02-15 15:12 ` Josh Boyer
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=200802110733.57267.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=weo@reccoware.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;
as well as URLs for NNTP newsgroup(s).