From: Kumar Gala <galak@kernel.crashing.org>
To: Liu Yu <Yu.Liu@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: patches for 2.6.25
Date: Wed, 23 Jan 2008 20:21:39 -0600 [thread overview]
Message-ID: <6AF85B0C-3EB6-42BA-9B61-CB3F95AACF59@kernel.crashing.org> (raw)
In-Reply-To: <6EBEC19BF4A8F843BCD6B9155BBE2515D52D1A@zch01exm26.fsl.freescale.net>
On Jan 23, 2008, at 7:51 PM, Liu Yu wrote:
>
> How about this one?
> http://patchwork.ozlabs.org/linuxppc/patch?id=15942
I've been trying to get some feedback from the glibc guys. The code
is pretty common and if the issues exists in one it exists in the
other.. I'm not sure if they have solved it some other way already.
- k
prev parent reply other threads:[~2008-01-24 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 16:43 patches for 2.6.25 Kumar Gala
2008-01-21 17:44 ` Jochen Friedrich
2008-01-21 18:04 ` Scott Wood
2008-01-24 1:51 ` Liu Yu
2008-01-24 2:21 ` Kumar Gala [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=6AF85B0C-3EB6-42BA-9B61-CB3F95AACF59@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Yu.Liu@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
/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).