From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: imx53 IPU support on 4.0.4
Date: Wed, 20 May 2015 21:55:54 +0100 [thread overview]
Message-ID: <20150520205554.GY2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <555C86A5.2030007@melag.de>
On Wed, May 20, 2015 at 03:05:41PM +0200, Enrico Weigelt, metux IT consult wrote:
> I've rebased the IPUv3 patches from ptx folks onto 4.0.4,
> working good for me. (now gst plays h264 @25fps on imx53)
>
> https://github.com/metux/linux/commits/submit-4.0-imx53-ipuv3
>
> (Haven't 4.1rc* yet, as it broke some other things for me.)
While it's useful to broadcast your work, please have some consideration
for the forum(s) you're doing that to.
The way kernel development works is that patches are sent to mailing
lists for review. Kernel developers review the patches and provide
comments back. The comments are discussed and actioned, and a new
set of patches posted for further review. This cycle repeats.
When everyone is happy, the patches can be applied, or pulled from
a non-github git tree. (Kernel people generally don't like github.)
This is so that upstream kernel developers don't get too overloaded
with work that really should be done by downstream folk (imagine if
they had to rewrite every patch that came their way...)
Thanks.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-05-20 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 13:05 Enrico Weigelt, metux IT consult
2015-05-20 13:21 ` Fabio Estevam
2015-05-28 12:35 ` Enrico Weigelt, metux IT consult
2015-05-20 20:55 ` Russell King - ARM Linux [this message]
2015-05-21 12:51 ` Nicolas Dufresne
2015-05-21 13:01 ` Fabio Estevam
2015-05-28 16:28 ` Enrico Weigelt, metux IT consult
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=20150520205554.GY2067@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=weigelt@melag.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
all inboxes | Powered by JetHome®