From: Romain Perier <romain.perier@collabora.com>
To: Trevor Woerner <twoerner@gmail.com>, ayaka <ayaka@soulik.info>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH v3 1/3] recipes-multimedia: add Rockchip MPP library
Date: Wed, 17 May 2017 08:48:37 +0200 [thread overview]
Message-ID: <c1ba3232-e5d0-0a15-c33f-8218d652ebee@collabora.com> (raw)
In-Reply-To: <20170516184422.GA1041@linux-uys3>
Hello,
Le 16/05/2017 à 20:44, Trevor Woerner a écrit :
> Randy,
>
> Neither of the issues that were identified in your v2 of this patch were
> addressed in this v3. Namely:
>
> 1) please use your real name (first, last) in your signed-off-by line
> 2) please don't create a package from this recipe whose name doesn't include
> the recipe name (i.e. please don't create "rockchip-vpu" from a recipe
> "rockchip-mpp"), suggestions were provided
>
> Aside from the email headers and the version of git used, this patch is
> identical to the v2 you submitted.
>
> Best regards,
> Trevor
+1
And please, include a changelog in your new version, at least in the
cover letter, something like:
Changes in v3:
- Item1 fixed
- Item2 fixed
Changes in v2:
- Item1 fixed
- Item2 fixed
Thanks,
Romain
next prev parent reply other threads:[~2017-05-17 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:18 [meta-rockchip] [PATCH v3 0/3] Add video codec recipes ayaka
2017-05-16 14:18 ` [PATCH v3 1/3] recipes-multimedia: add Rockchip MPP library ayaka
2017-05-16 18:44 ` Trevor Woerner
2017-05-17 6:48 ` Romain Perier [this message]
2017-05-17 7:28 ` Ayaka
2017-05-16 14:18 ` [PATCH v3 2/3] recipes-multimedia: add gstreamer rockchip support ayaka
2017-05-16 14:18 ` [PATCH v3 3/3] recipes-multimedia: images: rockchip media image ayaka
2017-05-16 14:24 ` [meta-rockchip] [PATCH v3 0/3] Add video codec recipes Khem Raj
2017-05-16 14:30 ` ayaka
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=c1ba3232-e5d0-0a15-c33f-8218d652ebee@collabora.com \
--to=romain.perier@collabora.com \
--cc=ayaka@soulik.info \
--cc=twoerner@gmail.com \
--cc=yocto@yoctoproject.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.