xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: lars.kurth.xen@gmail.com, xen-devel@lists.xenproject.org,
	Dirk Behme <dirk.behme@de.bosch.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform
Date: Thu, 7 Jul 2016 12:28:54 +0100	[thread overview]
Message-ID: <20160707112854.GJ416@citrix.com> (raw)
In-Reply-To: <577A44B4.5000705@arm.com>

Also CC Lars.

On Mon, Jul 04, 2016 at 12:12:52PM +0100, Julien Grall wrote:
> (CC Wei for the release part)
> 
> Hi Dirk,
> 
> On 04/07/16 07:51, Dirk Behme wrote:
> >Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> 
> Thank you for adding support of a new board in Xen.
> 
> During the last hackathon, we discussed about improving pre-release testing
> on ARM hardware [1] and helping users to boot Xen on supported board.
> 
> This patch is the first board officially supported since then, so I would
> like to start applying what was discussed (I will put on a wiki page later).
> Below the list of things that I would like to see when a new board is added:
> 
>    - Create a wiki page to explain the requirements to boot Xen on the board
> (e.g new firmware if not supported out of box, linux version,...);
>    - Add a link to the new page in [2];
>    - Add the contact details in [3] of someone who would could test
> pre-release and help out users to boot Xen on the board.
> 
> I do not expect the latter point to be time consuming. It is basically
> checking if Xen boots before each release and possibly update the
> requirements of the board. For the part helping users, it will mostly be
> question related to booting Xen on the hardware. Others may not be able to
> answer because they do not have the board on their desk.
> 
 
FWIW having some wiki pages, and most importantly contact details, would
be a good starting point.

Can we also have a section in MAINTAINERS for different boards (or a
dedicated file?) so that we can easily gather all contact and send
emails in a batch when the release is near?

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-07-07 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04  6:51 [PATCH] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform Dirk Behme
2016-07-04 11:12 ` Julien Grall
2016-07-07 11:28   ` Wei Liu [this message]
2016-07-07 12:43     ` Lars Kurth
2016-07-07 13:14       ` Julien Grall
2016-07-07 13:17         ` Lars Kurth
2016-07-07 13:20           ` Andrew Cooper
2016-07-07 13:31             ` Stefano Stabellini
2016-07-07 13:43         ` Wei Liu

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=20160707112854.GJ416@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).