From: Hans Verkuil <hverkuil@xs4all.nl>
To: Rick Chang <rick.chang@mediatek.com>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
srv_heupstream@mediatek.com, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Minghsiu Tsai <minghsiu.tsai@mediatek.com>
Subject: Re: [PATCH v6 3/3] arm: dts: mt2701: Add node for Mediatek JPEG Decoder
Date: Tue, 22 Nov 2016 13:43:34 +0100 [thread overview]
Message-ID: <badf8125-27ed-9c5b-fbc0-75716ffdfb0e@xs4all.nl> (raw)
In-Reply-To: <1479784905.8964.15.camel@mtksdaap41>
On 22/11/16 04:21, Rick Chang wrote:
> Hi Hans,
>
> On Mon, 2016-11-21 at 15:51 +0100, Hans Verkuil wrote:
>> On 17/11/16 04:38, Rick Chang wrote:
>>> Signed-off-by: Rick Chang <rick.chang@mediatek.com>
>>> Signed-off-by: Minghsiu Tsai <minghsiu.tsai@mediatek.com>
>>> ---
>>> This patch depends on:
>>> CCF "Add clock support for Mediatek MT2701"[1]
>>> iommu and smi "Add the dtsi node of iommu and smi for mt2701"[2]
>>>
>>> [1] http://lists.infradead.org/pipermail/linux-mediatek/2016-October/007271.html
>>> [2] https://patchwork.kernel.org/patch/9164013/
>>
>> I assume that 1 & 2 will appear in 4.10? So this patch needs to go in
>> after the
>> other two are merged in 4.10?
>>
>> Regards,
>>
>> Hans
>
> [1] will appear in 4.10, but [2] will appear latter than 4.10.So this
> patch needs to go in after [1] & [2] will be merged in 4.11.
So what should I do? Merge the driver for 4.11 and wait with this patch
until [2] is merged in 4.11? Does that sound reasonable?
Regards,
Hans
next prev parent reply other threads:[~2016-11-22 12:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 3:38 [PATCH v6 0/3] Add Mediatek JPEG Decoder Rick Chang
2016-11-17 3:38 ` [PATCH v6 1/3] dt-bindings: mediatek: Add a binding for " Rick Chang
2016-11-17 3:38 ` [PATCH v6 2/3] vcodec: mediatek: Add Mediatek JPEG Decoder Driver Rick Chang
2016-11-17 3:38 ` [PATCH v6 3/3] arm: dts: mt2701: Add node for Mediatek JPEG Decoder Rick Chang
2016-11-21 14:51 ` Hans Verkuil
2016-11-22 3:21 ` Rick Chang
2016-11-22 12:43 ` Hans Verkuil [this message]
2016-11-23 1:54 ` Rick Chang
2016-11-23 9:43 ` Rick Chang
2017-01-06 2:34 ` Rick Chang
2017-01-09 11:29 ` Hans Verkuil
2017-01-09 18:45 ` Matthias Brugger
2017-01-09 18:47 ` Matthias Brugger
2017-01-10 1:28 ` Eddie Huang
2017-01-13 15:02 ` Matthias Brugger
2017-02-09 2:10 ` Rick Chang
2017-02-13 10:42 ` Hans Verkuil
2016-11-21 14:53 ` [PATCH v6 0/3] Add " Hans Verkuil
2016-11-22 3:12 ` Rick Chang
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=badf8125-27ed-9c5b-fbc0-75716ffdfb0e@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=minghsiu.tsai@mediatek.com \
--cc=rick.chang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).