From: nicolas.dufresne@collabora.com (Nicolas Dufresne)
To: linux-arm-kernel@lists.infradead.org
Subject: imx53 IPU support on 4.0.4
Date: Thu, 21 May 2015 08:51:25 -0400 [thread overview]
Message-ID: <1432212685.11730.6.camel@collabora.com> (raw)
In-Reply-To: <20150520205554.GY2067@n2100.arm.linux.org.uk>
Le mercredi 20 mai 2015 ? 21:55 +0100, Russell King - ARM Linux a ?crit
:
> 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.
This patchset is already in the queue, so nothing to be done here.
@Fabio, you simply have to be patient.
Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>,
"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: Thu, 21 May 2015 08:51:25 -0400 [thread overview]
Message-ID: <1432212685.11730.6.camel@collabora.com> (raw)
In-Reply-To: <20150520205554.GY2067@n2100.arm.linux.org.uk>
Le mercredi 20 mai 2015 à 21:55 +0100, Russell King - ARM Linux a écrit
:
> 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.
This patchset is already in the queue, so nothing to be done here.
@Fabio, you simply have to be patient.
Nicolas
next prev parent reply other threads:[~2015-05-21 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 13:05 imx53 IPU support on 4.0.4 Enrico Weigelt, metux IT consult
2015-05-20 13:05 ` Enrico Weigelt, metux IT consult
2015-05-20 13:21 ` Fabio Estevam
2015-05-20 13:21 ` Fabio Estevam
2015-05-28 12:35 ` Enrico Weigelt, metux IT consult
2015-05-28 12:35 ` Enrico Weigelt, metux IT consult
2015-05-20 20:55 ` Russell King - ARM Linux
2015-05-20 20:55 ` Russell King - ARM Linux
2015-05-21 12:51 ` Nicolas Dufresne [this message]
2015-05-21 12:51 ` Nicolas Dufresne
2015-05-21 13:01 ` Fabio Estevam
2015-05-21 13:01 ` Fabio Estevam
2015-05-28 16:28 ` Enrico Weigelt, metux IT consult
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=1432212685.11730.6.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.