From: Philipp Zabel <p.zabel@pengutronix.de>
To: Peter Seiderer <ps.report@gmx.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Steve Longerbeam <slongerbeam@gmail.com>
Cc: linux-media@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] media: staging/imx: fill vb2_v4l2_buffer sequence entry
Date: Tue, 12 Jun 2018 10:41:35 +0200 [thread overview]
Message-ID: <1528792895.5280.7.camel@pengutronix.de> (raw)
In-Reply-To: <20180611224833.64a89c80@gmx.net>
Hi,
On Mon, 2018-06-11 at 22:48 +0200, Peter Seiderer wrote:
> Hello *,
>
> On Fri, 16 Mar 2018 10:05:44 -0700, Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
> > Reviewed-by: Steve Longerbeam <steve_longerbeam@mentor.com>
>
> Ping? Anybody taking this one?
The patches have been marked not applicable in patchwork [1][2].
They do apply on media_tree master.
[1] https://patchwork.linuxtv.org/patch/47946/
[2] https://patchwork.linuxtv.org/patch/47947/
regards
Philipp
next prev parent reply other threads:[~2018-06-12 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 19:13 [PATCH v4 1/2] media: staging/imx: fill vb2_v4l2_buffer field entry Peter Seiderer
2018-03-15 19:13 ` [PATCH v4 2/2] media: staging/imx: fill vb2_v4l2_buffer sequence entry Peter Seiderer
2018-03-16 8:12 ` Dan Carpenter
2018-03-16 17:05 ` Steve Longerbeam
2018-06-11 20:48 ` Peter Seiderer
2018-06-12 8:41 ` Philipp Zabel [this message]
2018-06-12 8:59 ` Hans Verkuil
2018-03-16 17:02 ` [PATCH v4 1/2] media: staging/imx: fill vb2_v4l2_buffer field entry Steve Longerbeam
2018-06-11 20:47 ` Peter Seiderer
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=1528792895.5280.7.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ps.report@gmx.net \
--cc=slongerbeam@gmail.com \
/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