public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Paul Walmsley <paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: Helping out with Tegra
Date: Sun, 16 Jun 2013 12:37:12 +0200	[thread overview]
Message-ID: <20130616103711.GB28222@manwe> (raw)
In-Reply-To: <alpine.DEB.2.02.1306050830350.8983-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

On Wed, Jun 05, 2013 at 08:31:15AM +0000, Paul Walmsley wrote:
> 
> Hi folks,
> 
> Just a quick note to say that I'll be helping out with the Tegra 
> upstreaming effort.  Hopefully will be able to help more than I harm ;-)
> 
> Eric Brower has graciously passed along a T33 "Beaver board".  As you've 
> probably seen, will plan to send periodic mainline basic test reports for 
> that board, along with any others I can get my hands on.

It'd be really useful to have something along the same lines for
linux-next. That's a lot more work because it should ideally be done on
a daily basis (or at least every day a linux-next tree is merged), but
it'll allow us to catch such bugs much earlier. Perhaps if you can
provide the scripts that you use we can spread the load.

On the other hand I suppose most people working on Tegra will run
linux-next on a daily basis anyway, so it'll be quite well tested.
Having automated tests on a wide variety of boards might still be useful
given how developers tend to stick to a small subset of devices for
daily work.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-06-16 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  8:31 Helping out with Tegra Paul Walmsley
     [not found] ` <alpine.DEB.2.02.1306050830350.8983-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2013-06-16 10:37   ` Thierry Reding [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=20130616103711.GB28222@manwe \
    --to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org \
    --cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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