From: Wolfram Sang <w.sang@pengutronix.de>
To: "B.J. Buchalter" <bj@mhlabs.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Question about tracking freescale patches for Linux
Date: Tue, 28 Jul 2009 10:31:00 +0200 [thread overview]
Message-ID: <20090728083059.GB3170@pengutronix.de> (raw)
In-Reply-To: <06A91D45-B506-44F8-A234-D9E55301349D@mhlabs.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
> I have contacted Freescale, but they basically say that they provide the
> BSP, and make no commitments to supporting any other version of the linux
> kernel.
So true :(
> 1) is there any way to determine if any these patches are currently
> being worked into the mainline kernel, or if they have been abandoned
> for some reason?
I usually use search engines (which often lead to linux-ppc threads) and
patchwork.ozlabs.org.
>
> 2) Is it worth trying to move these patches up to the head of
> development and trying to get them merged into the mainline kernel, or
> is that really just up to freescale to do?
It surely is worth (and is often done by people not involved with fsl). But be
warned, some patches are in a terrible state, meaning half a rewrite is
necessary.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-28 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 6:08 Question about tracking freescale patches for Linux B.J. Buchalter
2009-07-28 8:31 ` Wolfram Sang [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=20090728083059.GB3170@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=bj@mhlabs.com \
--cc=linuxppc-dev@lists.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