From: Xianghua Xiao <x.xiao@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8641(D) software status
Date: Thu, 11 May 2006 14:24:29 -0500 [thread overview]
Message-ID: <44638F6D.1030602@freescale.com> (raw)
In-Reply-To: <20060511190201.D3818352B0C@atlas.denx.de>
well I am not the one to be allowed to send public patches. However if
someone needs a 2.6.15/2.6.16 patch I can certainly send it out before a
public release(2.6.17?) is ready. It's also available on freescale's
website.
thanks,
xianghua
Wolfgang Denk wrote:
>In message <44634541.3040109@freescale.com> you wrote:
>
>
>>We have patches for 8641D against 2.6.15/2.6.16 and it works well in lab
>>in the last three months along with u-boot code. I think a patch against
>>2.6.17 or later will be released in the future. However if you need the
>>2.6.15/2.6.16 patch now, you can contact Freescale directly. In fact,
>>for all 8641D boards we will ship, we will include the kernel/u-boot
>>source code on the SATA hard drive directly as well, or you can also
>>download them from freescale's website.
>>
>>
>
>And when will you start working with the commmunity, and submit your
>patches to the public source tree? Will Freescale wait (again) until
>they are against such an old version that it's a PITA to merge them?
>
>Best regards,
>
>Wolfgang Denk
>
>
>
--
// Xianghua Xiao
// Freescale Semiconductor x.xiao@freescale.com
// (Tel)1 (512) 996-6768 (Fax) 1 (512) 996-7438
// 7700 W. Parmer Lane, MD: PL30, Austin, TX 78729
next prev parent reply other threads:[~2006-05-11 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 13:53 MPC8641(D) software status Sam Song
2006-05-11 14:08 ` Xianghua Xiao
2006-05-11 19:02 ` Wolfgang Denk
2006-05-11 19:24 ` Xianghua Xiao [this message]
2006-05-11 19:55 ` Wolfgang Denk
2006-05-12 1:31 ` Sam Song
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=44638F6D.1030602@freescale.com \
--to=x.xiao@freescale.com \
--cc=linuxppc-embedded@ozlabs.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).