linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic.nl>
To: linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>, Wolfgang Denk <wd@denx.de>,
	Gunnar Von Boehn <gunnar@genesi-usa.com>
Subject: Re: [RFC] [PATCH v2] MPC5121 TLB errata workaround
Date: Fri, 13 Mar 2009 11:26:28 +0100	[thread overview]
Message-ID: <200903131126.28662.david.jander@protonic.nl> (raw)
In-Reply-To: <200903131121.00077.david.jander@protonic.nl>


Forgot to mention: The patch is based on denx git tree head 'ads5121', but 
it should apply without problem (some offset at most) to mainline.

Best regards,

-- 
David Jander
Protonic Holland.

  reply	other threads:[~2009-03-13 10:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 10:20 [RFC] [PATCH v2] MPC5121 TLB errata workaround David Jander
2009-03-13 10:26 ` David Jander [this message]
2009-03-13 13:22   ` Kumar Gala
2009-03-13 14:16     ` David Jander
2009-03-13 13:21 ` Kumar Gala
2009-03-13 14:24   ` David Jander
2009-03-13 15:23     ` Kumar Gala
2009-03-16 10:44       ` David Jander
2009-03-16 11:41         ` Kumar Gala

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=200903131126.28662.david.jander@protonic.nl \
    --to=david.jander@protonic.nl \
    --cc=gunnar@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=wd@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;
as well as URLs for NNTP newsgroup(s).