All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH VSP test suite] Remove dependency on a particular yavta branch
Date: Sat, 23 Feb 2019 02:45:50 +0100	[thread overview]
Message-ID: <20190223014550.GT11484@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20190222100257.4847-1-laurent.pinchart@ideasonboard.com>

Hi Laurent,

Thanks for your patch.

On 2019-02-22 12:02:57 +0200, Laurent Pinchart wrote:
> All the changes required by the VSP test suite have been integrated in
> the master branch of yavta. There is no need to depend on the vsp branch
> anymore, remove the corresponding paragraph from the documentation.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

> ---
>  README | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/README b/README
> index 17920ee663c8..0d5a6967d7f5 100644
> --- a/README
> +++ b/README
> @@ -45,10 +45,6 @@ system in a directory included in $PATH.
>  * raw2rgbpnm (available at git://git.retiisi.org.uk/~sailus/raw2rgbpnm.git)
>  * yavta (available at git://git.ideasonboard.org/yavta.git)
>  
> -All but the HGO and CLU/LUT tests can be run with the latest version of these
> -tools. To test the HGO, HGT and CLU/LUT, the 'vsp' branch of 'yavta' is currently
> -needed.
> -
>  The following tool is additionally required to run some of the tests. If the
>  tool is not available the corresponding tests will be skipped.
>  
> -- 
> Regards,
> 
> Laurent Pinchart
> 

-- 
Regards,
Niklas Söderlund

      reply	other threads:[~2019-02-23  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 10:02 [PATCH VSP test suite] Remove dependency on a particular yavta branch Laurent Pinchart
2019-02-23  1:45 ` Niklas Söderlund [this message]

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=20190223014550.GT11484@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.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.