From: Hans Verkuil <hverkuil@xs4all.nl>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, robh+dt@kernel.org, mchehab@kernel.org,
tfiga@chromium.org, dshah@xilinx.com,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 3/5] media: dt-bindings: media: Add vendor prefix for allegro
Date: Mon, 27 May 2019 16:58:38 +0200 [thread overview]
Message-ID: <c1f2aa85-4d6e-86a7-b627-a0463ff5e802@xs4all.nl> (raw)
In-Reply-To: <20190527165729.540d457e@litschi.hi.pengutronix.de>
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 only this patch?
Up to you, I have no preference.
Regards,
Hans
>
> Michael
>
>>
>> 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 suites and H.264/AVC, H.265/HEVC, and
>>> VP9 encoder, codec and decoder hardware (RTL) IPs.
>>>
>>> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>> ---
>>> v5 -> v6:
>>> none
>>>
>>> v5:
>>> - new patch
>>> ---
>>> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
>>> index 8162b0eb4b50..78a849b25f64 100644
>>> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
>>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
>>> @@ -16,6 +16,7 @@ adi Analog Devices, Inc.
>>> advantech Advantech Corporation
>>> aeroflexgaisler Aeroflex Gaisler AB
>>> al Annapurna Labs
>>> +allegro Allegro DVT
>>> allo Allo.com
>>> allwinner Allwinner Technology Co., Ltd.
>>> alphascale AlphaScale Integrated Circuits Systems, Inc.
>>>
>>
>>
next prev parent reply other threads:[~2019-05-27 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 17:21 [PATCH v6 0/5] Add ZynqMP VCU/Allegro DVT H.264 encoder driver Michael Tretter
2019-05-13 17:21 ` [PATCH v6 1/5] videobuf2-v4l2: set last_buffer_dequeued in dqbuf Michael Tretter
2019-05-13 17:21 ` [PATCH v6 2/5] media: dt-bindings: media: document allegro-dvt bindings Michael Tretter
2019-05-13 17:21 ` [PATCH v6 3/5] media: dt-bindings: media: Add vendor prefix for allegro Michael Tretter
2019-05-17 2:31 ` Rob Herring
2019-05-27 14:35 ` Hans Verkuil
2019-05-27 14:57 ` Michael Tretter
2019-05-27 14:58 ` Hans Verkuil [this message]
2019-05-13 17:21 ` [PATCH v6 4/5] [media] allegro: add Allegro DVT video IP core driver Michael Tretter
2019-05-13 17:21 ` [PATCH v6 5/5] [media] allegro: add SPS/PPS nal unit writer Michael Tretter
2019-05-22 12:04 ` [PATCH v6 0/5] Add ZynqMP VCU/Allegro DVT H.264 encoder driver Hans Verkuil
2019-05-22 13:49 ` Michael Tretter
2019-05-27 13:45 ` Michael Tretter
2019-05-27 14:30 ` Hans Verkuil
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=c1f2aa85-4d6e-86a7-b627-a0463ff5e802@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=devicetree@vger.kernel.org \
--cc=dshah@xilinx.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tfiga@chromium.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 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).