public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom•gr>
To: Wrobel Heinz-r39252 <Heinz.Wrobel@freescale•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [RFC] [PATCH] ppc32: workaround for spurious IRQs on PQ2
Date: Wed, 27 Apr 2005 10:39:03 +0300	[thread overview]
Message-ID: <426F4197.9020600@intracom.gr> (raw)
In-Reply-To: <DF02D66C37C26B4C8018BF84F0E37FEC08440764@zwg18exm01.ea.freescale.net>

Wrobel Heinz-r39252 wrote:
> Eugene,
> 
> check slides 17, 20-22 out of my SNDF 2004 presentation H1125 found at
> http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=052577pzMPYZjg286165422098
> 
> ... and attend the June 2005 FTF in Orlando ...
> http://www.freescale.com/ftf *grin*
> 
> Heinz
>  

Heh, I *was* on SNDF 2004, but I didn't attend this presentation.

Heinz, try to get a supplement on the web site...

Regards

Pantelis

  parent reply	other threads:[~2005-04-27  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27  6:54 [RFC] [PATCH] ppc32: workaround for spurious IRQs on PQ2 Wrobel Heinz-r39252
2005-04-27  7:15 ` Eugene Surovegin
2005-04-27  7:39 ` Pantelis Antoniou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-26 19:21 Eugene Surovegin

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=426F4197.9020600@intracom.gr \
    --to=panto@intracom$(echo .)gr \
    --cc=Heinz.Wrobel@freescale$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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