On 5/27/19 4:57 PM, Michael Tretter wrote:
> On Mon, 27 May 2019 16:35:24 +0200, Hans Verkuil wrote:
>> This patch no longer applies (vendor-prefixes.txt is now
>> vendor-prefixes.yaml).
>> Can you rebase this patch?
>
> Should I rebase the entire series and send a v7 or is it enough to
> rebase
On Mon, 27 May 2019 16:35:24 +0200, Hans Verkuil wrote:
> This patch no longer applies (vendor-prefixes.txt is now
> vendor-prefixes.yaml).
> Can you rebase this patch?
Should I rebase the entire series and send a v7 or is it enough to
rebase only this patch?
Michael
>
> Regards,
>
> Ha
Hi Michael,
This patch no longer applies (vendor-prefixes.txt is now vendor-prefixes.yaml).
Can you rebase this patch?
Regards,
Hans
On 5/13/19 7:21 PM, Michael Tretter wrote:
> Add vendor prefix for Allegro DVT, a provider of H.264/AVC, H.265/HEVC,
> AVS2, VP9 and AV1 compliance test s
On Mon, May 13, 2019 at 12:21 PM Michael Tretter
wrote:
>
> Add vendor prefix for Allegro DVT, a provider of H.264/AVC, H.265/HEVC,
> AVS2, VP9 and AV1 compliance test suites and H.264/AVC, H.265/HEVC, and
> VP9 encoder, codec and decoder hardware (RTL) IPs.
>
> Signed-off-by: Michael Tretter
> R
Add vendor prefix for Allegro DVT, a provider of H.264/AVC, H.265/HEVC,
AVS2, VP9 and AV1 compliance test suites and H.264/AVC, H.265/HEVC, and
VP9 encoder, codec and decoder hardware (RTL) IPs.
Signed-off-by: Michael Tretter
Reviewed-by: Rob Herring
---
v5 -> v6:
none
v5:
- new patch
---
Docu
