From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: "'Li Yang-r58472'" <LeoLi@freescale.com>, <pantelis@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux 2.6.x : cpm_dpalloc alignment bug perhaps not fully resolved
Date: Wed, 5 Jul 2006 10:25:55 +0200 [thread overview]
Message-ID: <003701c6a00c$a9284c40$5201a8c0@GEG2400> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD467306FA6F52@zch01exm40.ap.freescale.net>
Hi Leo,
Thanks for the reply.
The patch, I already applied, comes directly from Pantelis
and is the same code as found at
http://patchwork.ozlabs.org/linuxppc/patch?id=3484
What do you mean by the alignment patch ?
I suspect a problem in the cpm_dpfree function,
not in the cpm_dpalloc function.
I'll try to give more details.
Best regards
Laurent
> -----Message d'origine-----
> De : Li Yang-r58472 [mailto:LeoLi@freescale.com]
> Envoyé : mer. 5 juillet 2006 03:32
> À : Laurent Lagrange; pantelis@embeddedalley.com
> Cc : linuxppc-embedded@ozlabs.org
> Objet : RE: Linux 2.6.x : cpm_dpalloc alignment bug perhaps not fully
> resolved
>
>
> Did you apply the alignment patch too? AFAIK, the problem is
> never fixed in
> mainstream trees.
>
> Best Regards,
> Leo
>
next prev parent reply other threads:[~2006-07-05 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 2:32 Linux 2.6.x : cpm_dpalloc alignment bug perhaps not fully r esolved Li Yang-r58472
2006-07-05 8:25 ` Laurent Lagrange [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-05 8:35 Li Yang-r58472
2006-07-05 9:11 ` Linux 2.6.x : cpm_dpalloc alignment bug perhaps not fully resolved Laurent Lagrange
2006-07-05 9:38 ` Pantelis Antoniou
2006-07-05 10:03 ` Laurent Lagrange
2006-01-25 16:14 Misunderstanding with function cpm_dpalloc in Linux 2.6.x Pantelis Antoniou
2006-07-04 15:37 ` Linux 2.6.x : cpm_dpalloc alignment bug perhaps not fully resolved Laurent Lagrange
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='003701c6a00c$a9284c40$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=LeoLi@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=pantelis@embeddedalley.com \
/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).