All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hiep Cao Minh <cm-hiep@jinso.co.jp>
Cc: "Ryusuke Sakato" <ryusuke.sakato.bx@renesas.com>,
	"kuninori morimoto" <kuninori.morimoto.gx@renesas.com>,
	"magnus Damm" <magnus.damm@gmail.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	稲吉 <h-inayoshi@jinso.co.jp>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	'Dung:人ソ' <nv-dung@jinso.co.jp>,
	"Xuan Truong Nguyen" <nx-truong@jinso.co.jp>,
	laurent.pinchart+renesas@ideasonboard.com,
	horms+renesas@verge.net.au, linux-renesas-soc@vger.kernel.org
Subject: Re: The failure summary report for linux stable v4.7
Date: Wed, 03 Aug 2016 20:38:26 +0300	[thread overview]
Message-ID: <14575379.WoFtKTTBW3@avalon> (raw)
In-Reply-To: <9ba4b58f-173f-71a7-8868-d577a5789a7e@jinso.co.jp>

Hello Hiep-san,

On Wednesday 03 Aug 2016 20:27:07 Hiep Cao Minh wrote:
> Hi all,
> 
> We would like to report the summary of the failure to ML, starting from
> Linux stable v4.7.
> 
> Before, we only reported each issue to the person in charge at the time
> of issue detection.
> 
> Now we think that the upstream version’s failure status quo should be
> updated usually to all upstream members.
> 
> So, first, we are going to report the Linux upstream issue summary for
> each version full test, then we report each issue to the person in charge.
> 
> Currently, we have full tests of upstream v4.x-rc2 and stable version,
> and reconfirm the issue of rc2 version on v4.x-rc7 (before stable
> version is released).
> 
> Between full test versions, we investigate and analyze the issue. We
> will report the investigated results if find out any useful information.
> 
> Before:
> 
> Only report the issue to the person in charge at the time of issue
> detection.
> 
> Sometimes re-report the issue to the person in charge.
> 
> After:
> 
> Usually update and report the summary of the issue to all members.
> 
> Usually report each issue and update the status quo to the person in charge.

Thank you for the report. I tried to reproduce the Lager HDMI output issue on 
mainline, and got blocked by the fact that HDMI output seems completely 
broken. I'm investigating that and will provide a fix, and then move on to the 
issue you've reported.

-- 
Regards,

Laurent Pinchart

           reply	other threads:[~2016-08-03 17:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <9ba4b58f-173f-71a7-8868-d577a5789a7e@jinso.co.jp>]

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=14575379.WoFtKTTBW3@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=cm-hiep@jinso.co.jp \
    --cc=geert+renesas@glider.be \
    --cc=h-inayoshi@jinso.co.jp \
    --cc=horms+renesas@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=nv-dung@jinso.co.jp \
    --cc=nx-truong@jinso.co.jp \
    --cc=ryusuke.sakato.bx@renesas.com \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    /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.