Hi Aníbal,
Whenever submitting a patch, please provide a commit message. Even if
it's trivial, there is something to be said. Why should we do the
update? Does it support new hardware? A particularly relevant feature?
If not, knowing it's just an update is useful information. Which
machines are impacted and what tessting has been performed (as Nitin
pointed out). In general, if it's worth submitting, it's worth documenting.
I'm going to throw these in to master-next for some testing, but please
resubmit today if you can with a commit message. (for both).
On 2/10/15 7:48 AM, Aníbal Limón wrote:> Signed-off-by: Aníbal Limón
<anibal.li...@linux.intel.com>
> ---
> common/recipes-multimedia/libva/{libva_1.4.1.bb => libva_1.5.0.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename common/recipes-multimedia/libva/{libva_1.4.1.bb => libva_1.5.0.bb}
> (42%)
>
> diff --git a/common/recipes-multimedia/libva/libva_1.4.1.bb
> b/common/recipes-multimedia/libva/libva_1.5.0.bb
> similarity index 42%
> rename from common/recipes-multimedia/libva/libva_1.4.1.bb
> rename to common/recipes-multimedia/libva/libva_1.5.0.bb
> index 23a499c..ae5078b 100644
> --- a/common/recipes-multimedia/libva/libva_1.4.1.bb
> +++ b/common/recipes-multimedia/libva/libva_1.5.0.bb
> @@ -2,5 +2,5 @@ require libva.inc
>
> SRC_URI =
> "http://www.freedesktop.org/software/vaapi/releases/libva/${BP}.tar.bz2";
>
> -SRC_URI[md5sum] = "8e3e7096750c14d1f98da807df7c1ba5"
> -SRC_URI[sha256sum] =
> "0662af0ecdf1cfd2bb47e86f5bf66009554fe12ce7bf5b9cec6a2cc43f3f4c11"
> +SRC_URI[md5sum] = "ad0b55794308ec397d249a0a2a6df27a"
> +SRC_URI[sha256sum] =
> "e946d4b3110e4e23ec6a588e0c828937e502c67196d1266214441fefc4b83486"
>
--
Darren Hart
Intel Open Source Technology Center
--
_______________________________________________
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
