[Xen-devel] [PATCH v2 4/6] Add Code Review Guide

From: Lars Kurth This document highlights what reviewers such as maintainers and committers look for when reviewing code. It sets expectations for code authors and provides a framework for code reviewers. Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen

[Xen-devel] [PATCH v2 6/6] Added Resolving Disagreement

From: Lars Kurth This guide provides Best Practice on identifying and resolving common classes of disagreement Signed-off-by: Lars Kurth -- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc

[Xen-devel] Moving next week's community call to Thu 10th

Hi all, because many of us will be at the Platform Security Summit next week, I propose to move the community call to Thu 10th at the usual time Regards Lars ___ Xen-devel mailing list Xen-devel@lists.xenproject.org

[Xen-devel] add_maintainers.pl issues / "canonical" subject prefixes for CI v2 (was Re: [PATCH] create-diff-object: more precisely identify .rodata sections)

+Ross + Doug On 19/09/2019, 10:30, "Julien Grall" wrote: Hi Lars, On 18/09/2019 13:14, Lars Kurth wrote: > > > On 18/09/2019, 12:15, "Julien Grall" wrote: > > Hi Ian, > > On 18/09/2019 11:4

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 12:27, "Wieczorkiewicz, Pawel" wrote: > On 18. Sep 2019, at 13:19, Julien Grall wrote: > > Hi Pawel, > > On 18/09/2019 11:44, Wieczorkiewicz, Pawel wrote: >>> On 18. Sep 2019, at 12:41, Ian Jackson wrote: >>> >>> Julien Grall

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 12:15, "Julien Grall" wrote: Hi Ian, On 18/09/2019 11:41, Ian Jackson wrote: > Julien Grall writes ("Re: [PATCH] create-diff-object: more precisely identify .rodata sections"): >> On 18/09/2019 10:52, Wieczorkiewicz, Pawel wrote: >>> $

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 11:44, "Wieczorkiewicz, Pawel" wrote: > On 18. Sep 2019, at 12:41, Ian Jackson wrote: > > Julien Grall writes ("Re: [PATCH] create-diff-object: more precisely identify .rodata sections"): >> On 18/09/2019 10:52, Wieczorkiewicz, Pawel wrote: >>> $

[Xen-devel] [PATCH XTF] Introduce a MAINTAINERS file

Rationale: this will allow us to use get_maintainer.pl / add_maintainers.pl scripts from xen.git Signed-off-by: Lars Kurth --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 MAINTAINERS diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index

[Xen-devel] [PATCH OSSTEST] Introduce a MAINTAINERS file

Rationale: this will allow us to use get_maintainer.pl / add_maintainers.pl scripts from xen.git Signed-off-by: Lars Kurth --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 MAINTAINERS diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index

[Xen-devel] [livepatch-build-tools] Add V: entry to maintainers

Usage of get_maintainers.pl now requires the V: entry under THE REST to identify a MAINTAINERS file in one of the Xen trees. See [1] [1] lists.xenproject.org/archives/html/xen-devel/2019-09/threads.html#00263 Signed-off-by: Lars Kurth --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff

Re: [Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

On 10/09/2019, 16:31, "Julien Grall" wrote: Hi, Actually, I have one question about the template (my ack still stands). On 9/10/19 4:18 PM, Julien Grall wrote: > Hi Lars, > > On 9/4/19 12:30 PM, Lars Kurth wrote: >> This c

[Xen-devel] [Vote] XCP-ng subproject proposal

Hello everyone, Olivier had posted an RFC for this proposal on xen-devel@- see https://xen.markmail.org/thread/ermnrb3ps3okvnjr The proposal also has been discussed by the Advisory Board and was approved However, for the proposal to fully

Re: [Xen-devel] [PATCH] Xen Project Code of Conduct

On 06/09/2019, 16:10, "Roger Pau Monne" wrote: On Wed, Sep 04, 2019 at 07:12:18PM +0100, Lars Kurth wrote: [...] > +## Conduct Team members > +Conduct Team members are project leadership team members from any > +sub-project. The current list of C

Re: [Xen-devel] Criteria for checking in core scheduling series

On 06/09/2019, 12:09, "George Dunlap" wrote: There was a discussion on the community call about the core scheduling series being developed by Juergen Gross [1]. The conclusion can be summarized as follows: * We normally wait to check in series until they are quite good

Re: [Xen-devel] [ANNOUNCE] Minutes for September 5th Community Call

Minutes are at https://cryptpad.fr/pad/#/2/pad/view/kpV4XxFWKjAF1fbIckIV87BVTRVRFlL913YWaFD0waI/embed/present/ and attached Lars 2019-09 Community Call.pdf Description: 2019-09 Community Call.pdf ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH] docs/sphinx: todo/wishlist

: Stefano Stabellini CC: Tim Deegan CC: Wei Liu CC: Julien Grall CC: Lars Kurth CC: Paul Durrant CC: Roger Pau Monné RFC for obvious reasons. A rendered version of this can be found at: https://andrewcoop-xen.readthedocs.io/en/docs-wishlis

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

> We can defer the xenstoreless name service topic to the October monthly call. > > For today's call, can we discuss the previously posted high-level design for > unification of the domB RFC with dom0less, as "domB mode" for > disaggregation of Xen's dom0? > > - domB mode for dom0less (July

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 09:33, "Juergen Gross" wrote: On 05.09.19 10:14, Andrew Cooper wrote: > On 05/09/2019 08:49, Lars Kurth wrote: >> On 05/09/2019, 08:41, "Rich Persaud" wrote: >> >> > On Sep 5, 2019, at 03:19, Jan Beulich w

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 08:50, "Jan Beulich" wrote: On 05.09.2019 09:41, Rich Persaud wrote: > If Xen community call topics are limited to escalations of xen-devel threads, then a new thread can be created for this topic. Xen community calls have also provided real-time, interactive feedback

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 08:41, "Rich Persaud" wrote: > On Sep 5, 2019, at 03:19, Jan Beulich wrote: > > Forgive me asking, but why is this put up as an agenda item here? > IMO this is the kind of thing where you would send a proposal and > request feedback by email first, and put

Re: [Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4)

On 04/09/2019, 19:12, "Lars Kurth" wrote: This series proposes a concrete version of the Xen Project CoC based on v1.4 of the Contributor Covenant. See [1] Apologies for the badly formatted patch. It seems the normal instructions do not work when using it on virgin git

[Xen-devel] [PATCH] Xen Project Code of Conduct

"project team" with "Conduct Team members" * Add e-mail alias * Add section on contacting individual Conduct Team members * Add section on Conduct Team members Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lis

[Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4)

/CoC-v1 Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc: committ...@xenproject.org Lars Kurth (2): Import v1.4 of Contributor Covenant CoC Xen Project Code of Conduct -- 2.13.0

[Xen-devel] [PATCH] Import v1.4 of Contributor Covenant CoC

Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc: committ...@xenproject.org --- code-of-conduct.md | 76 ++ 1

[Xen-devel] [Poll] Please vote on date options for next year's Developer Summit (closes Wednesday, September 11)

Hi all, we started planning next year’s Developer Summit, which is due to be in Europe. We have a venue in Bucharest, Romania secured but are still working through the details. As we are early, we do have several date options: so I wanted to give you a choice to vote, such that we end up with

[Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

Hi all, the proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/xwUTm6b5f5ijPTQcF9IFgkBg/ and you can edit to add items Alternatively, you can reply to this mail directly Agenda items appreciated ASAP: please put your name besides items if you edit the document Apologies for dropping

Re: [Xen-devel] Please propose agenda items for Thursday's community call

On 04/09/2019, 13:35, "Jan Beulich" wrote: On 03.09.2019 20:37, Lars Kurth wrote: > I have not gotten around to draft an agenda yet. Please reply to > this thread with possible agenda items. I will reply to this > thread with meeting invite and details as

[Xen-devel] [PATCH v4 1/3] Remove hardcoding from scripts/add_maintainers.pl

Instead of using a hardcoded location, inherit the location from $0 Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/add_maintainers.pl b/scripts/add_maintainers.pl index 09e9f66..5a6d0f6 100755

[Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

Signed-off-by: Lars Kurth Acked-by: Jan Beulich --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 77413e0..bb3da43 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -97,6 +97,9 @@ Descriptions of section

[Xen-devel] [PATCH v4 0/3] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

and fixed typo * Removed unused variable Lars Kurth (3): Remove hardcoding from scripts/add_maintainers.pl Add V section entry to allow identification of Xen MAINTAINERS file Add logic to use V section entry in THE REST for identifying xen trees MAINTAINERS| 4

[Xen-devel] [PATCH v4 3/3] Add logic to use V section entry in THE REST for identifying xen trees

Specifically: * Move check until after the MAINTAINERS file has been read * Add get_xen_maintainers_file_version() for check * Remove top_of_tree as not needed any more * Fail with extended error message when used out of tree Signed-off-by: Lars Kurth --- scripts/get_maintainer.pl | 57

[Xen-devel] Please propose agenda items for Thursday's community call

Folks, I have not gotten around to draft an agenda yet. Please reply to this thread with possible agenda items. I will reply to this thread with meeting invite and details as usual Regards Lars ___ Xen-devel mailing list Xen-devel@lists.xenproject.org

Re: [Xen-devel] [RFC] Code of Conduct

On 02/09/2019, 16:49, "Ian Jackson" wrote: Lars Kurth writes ("Re: [Xen-devel] [RFC] Code of Conduct"): > I attached a redline version of both the original (based on the LF events CoC) and a redline version based on the covenant given the constraints we agreed

Re: [Xen-devel] [PATCH v3 3/3] Add logic to use V section entry in THE REST for identifying xen trees

On 02/09/2019, 09:08, "Jan Beulich" wrote: On 30.08.2019 22:09, Lars Kurth wrote: > Specifically: > * Move check until after the MAINTAINERS file has been read > * Add get_xen_maintainers_file_version() for check > * Remove top_of_tree as not needed

[Xen-devel] [PATCH v3 3/3] Add logic to use V section entry in THE REST for identifying xen trees

Specifically: * Move check until after the MAINTAINERS file has been read * Add get_xen_maintainers_file_version() for check * Remove top_of_tree as not needed any more * Faiul with extended error message when used out of tree Signed-off-by: Lars Kurth --- scripts/get_maintainer.pl | 58

[Xen-devel] [PATCH v3 0/3] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

Changes in v2: * Remove debug message Changes in v3: * Split patch * add_maintainers.pl: do not issue a warning * add_maintainers.pl: introduce processing logic for V: tag * MAINTAINERS: Add V: tag to file Lars Kurth (3): Remove hardcoding

[Xen-devel] [PATCH v3 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

Signed-off-by: Lars Kurth --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 77413e0..bb3da43 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -97,6 +97,9 @@ Descriptions of section entries

[Xen-devel] [PATCH v3 1/3] Remove hardcoding from scripts/add_maintainers.pl

Instead of using a hardcoded location, inherit the location from $0 Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/add_maintainers.pl b/scripts/add_maintainers.pl index 09e9f66..5a6d0f6 100755

[Xen-devel] Added workflow docs for git-series

See https://wiki.xenproject.org/wiki/Managing_Xen_Patches_with_Git-series It solves some problems with git and makes managing series a little easier, but you still have to use autosquash So, it's not perfect Lars ___ Xen-devel mailing list

Re: [Xen-devel] [RFC] Code of Conduct

On 27/08/2019, 17:54, "Stefano Stabellini" wrote: On Tue, 27 Aug 2019, Lars Kurth wrote: > On 27/08/2019, 10:33, "Ian Jackson" wrote: > > Lars Kurth writes ("Re: [Xen-devel] [RFC] Code of Conduct"): > > I did raise

Re: [Xen-devel] [RFC] Code of Conduct

From: Rich Persaud Date: Friday, 16 August 2019 at 16:49 To: George Dunlap Cc: Lars Kurth , xen-devel , "minios-de...@lists.xenproject.org" , "mirageos-de...@lists.xenproject.org" , "win-pv-de...@lists.xenproject.org" , "committ...@xenproject.org&quo

Re: [Xen-devel] [PATCH v2] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

On 16/08/2019, 06:43, "Lars Kurth" wrote: > On 16 Aug 2019, at 14:28, Julien Grall wrote: > > > > On 16/08/2019 13:17, Lars Kurth wrote: >> On 16/08/2019, 11:01, "Julien Grall" wrote: >> Fro

Re: [Xen-devel] [RFC] Code of Conduct

From: Rich Persaud Date: Friday, 16 August 2019 at 16:49 To: George Dunlap Cc: Lars Kurth , xen-devel , "minios-de...@lists.xenproject.org" , "mirageos-de...@lists.xenproject.org" , "win-pv-de...@lists.xenproject.org" , "committ...@xenproject.org&quo

Re: [Xen-devel] [PATCH v2] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

> On 16 Aug 2019, at 14:28, Julien Grall wrote: > > > > On 16/08/2019 13:17, Lars Kurth wrote: >> On 16/08/2019, 11:01, "Julien Grall" wrote: >> From my understanding, any use on mini-os.git & co will be legitimate. >> However, &

Re: [Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos

On 16/08/2019, 13:09, "Paul Durrant" wrote: > -Original Message- > From: Lars Kurth > Sent: 16 August 2019 13:05 > To: Anthony Perard ; Julien Grall > Cc: xen-devel@lists.xenproject.org; Felipe Huici ; Stefano Stabellini > ; Wei

Re: [Xen-devel] [PATCH v2] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

On 16/08/2019, 11:01, "Julien Grall" wrote: Hi Lars, Thank you for the patch. On 15/08/2019 18:22, Lars Kurth wrote: > Use-case: Allow using both scripts on xen repositories such as > mini-os.git, osstest.git, > > Tool changes:

Re: [Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos

Added Paul Durrant On 16/08/2019, 12:17, "Anthony PERARD" wrote: On Fri, Aug 16, 2019 at 11:55:16AM +0100, Julien Grall wrote: > Hi Lars, > > On 16/08/2019 11:42, Lars Kurth wrote: > > Unikraft repos follow the same syntax as xen.git with the

Re: [Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos

Hi Julien, On 16/08/2019, 11:55, "Julien Grall" wrote: Hi Lars, On 16/08/2019 11:42, Lars Kurth wrote: > Unikraft repos follow the same syntax as xen.git with the > following exceptions: > * MAINTAINERS files are called MAINTAINERS.md &g

[Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos

: ... blocks Signed-off-by: Lars Kurth --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson Cc: Jan Beulich Cc: Julien Grall Cc: Konrad Rzeszutek Wilk Cc: Stefano Stabellini Cc: Tim Deegan Cc: Wei Liu CC: Simon Kuenzer CC: Florian Schmidt CC: Felipe Huici --- scripts

Re: [Xen-devel] [RFC] Code of Conduct

> On 15 Aug 2019, at 20:08, Rich Persaud wrote: > > Following the discussion we had at the Developer Summit (see > https://wiki.xenproject.org/wiki/Design_Sessions_2019#Community_Issues_.2F_Improvements_-_Communication.2C_Code_of_Conduct.2C_etc > >

Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation

> On 15 Aug 2019, at 17:29, Andrew Cooper wrote: > > On 15/08/2019 16:42, Wieczorkiewicz, Pawel wrote: >> Thanks Julien. I will do that next time (unless you guys want me to >> re-send all this ;-)). >> >> BTW, I also pushed my changes onto the xenbits server: >>

Re: [Xen-devel] [win-pv-devel] [RFC] Code of Conduct

> On 15 Aug 2019, at 19:27, Rich Persaud wrote: > > On Aug 15, 2019, at 14:01, Lars Kurth wrote: > >> Hi Rich, >> >> thanks for the feedback. I am going to >> >> On 15/08/2019, 18:23, "Rich Persaud" wrote: >&

[Xen-devel] [PATCH LIVEPATCH-BUILD-TOOLS] Introduce a MAINTAINERS file

Rationale: this will allow us to use get_maintainer.pl / add_maintainers.pl scripts from xen.git Signed-off-by: Lars Kurth --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 MAINTAINERS diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index

Re: [Xen-devel] [RFC] Code of Conduct

Hi Rich, thanks for the feedback. I am going to On 15/08/2019, 18:23, "Rich Persaud" wrote: > On Aug 9, 2019, at 13:48, Lars Kurth wrote: > > Hi all, Hi Lars, > > Following the discussion we had at the Developer Summit (see ht

[Xen-devel] [PATCH v2] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

: MAINTAINER1 M: MAINTAINER2 L: xen-devel@lists.xenproject.org S: Supported F: */ Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 4 ++-- scripts/get_maintainer.pl | 13 +++-- 2 files changed, 13 insertions

Re: [Xen-devel] [PATCH] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

On 15/08/2019, 18:12, "Lars Kurth" wrote: Use-case: Allow using both scripts on xen repositories such as mini-os.git, osstest.git, Tool changes: * add_maintainers.pl: $get_maintainer inherits path from $0 * get_maintainer.pl: warn (instead fo die) w

[Xen-devel] [PATCH] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

: MAINTAINER1 M: MAINTAINER2 L: xen-devel@lists.xenproject.org S: Supported F: */ Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 9 ++--- scripts/get_maintainer.pl | 13 +++-- 2 files changed, 17

Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation

> On 15 Aug 2019, at 16:58, Julien Grall wrote: > > Hi Lars, > > On 15/08/2019 16:46, Lars Kurth wrote: >>> On 15 Aug 2019, at 16:33, Lars Kurth >> <mailto:lars.kurth@gmail.com>> wrote: >>> >>> >>> >>>>

Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation

> On 15 Aug 2019, at 16:33, Lars Kurth wrote: > > > >> On 15 Aug 2019, at 16:19, Wieczorkiewicz, Pawel > <mailto:wipa...@amazon.de>> wrote: >> >> Hi Lars, Julien, >> >> Thanks for the pointers, I will read them up and follow the reco

Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation

rack some of the changes. I have not had time to add this to the docs yet Lars > > Best Regards, > Pawel Wieczorkiewicz > > > >> On 15. Aug 2019, at 16:58, Lars Kurth > <mailto:lars.kurth@gmail.com>> wrote: >> >> >> >>> On 15 Aug 2

Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation

> On 15 Aug 2019, at 12:38, Julien Grall wrote: > > Hi, > > I am not going to answer on the patch itself but the process. > > Any series (i.e more than one patch) should contain a cover letter with a > rough summary of the goal of the series. > > Furthermore, this 3 patches series has been

Re: [Xen-devel] [RFC] Code of Conduct

Perfect: I updated this also in the google doc. I will leave the review open for a week or two (we do have summer holidays after all) and let people comment. I can then send a proper proposal, followed by a vote Lars On 12/08/2019, 15:35, "George Dunlap" wrote: On 8/12/19 3:2

Re: [Xen-devel] Terminology for "guest" - Was: [PATCH] docs/sphinx: Introduction

On 13/08/2019, 09:43, "George Dunlap" wrote: > On Aug 13, 2019, at 3:59 AM, Sarah Newman wrote: > > On 8/12/19 8:01 AM, Andrew Cooper wrote: >> On 12/08/2019 15:53, George Dunlap wrote: >>> On 8/8/19 10:13 AM, Julien Grall wrote: Hi Jan,

[Xen-devel] [ANNOUNCE] Xen Project Developer Summit 2019: Slides, Recordings and Design Session notes are available

Dear Community member, if you didn’t make it to the developer summit, you can find material related to the summit in the following locations Slides: https://www.slideshare.net/search/slideshow?searchfrom=header=XPDDS19 YouTube playlist of recordings

Re: [Xen-devel] [RFC] Code of Conduct

Hi George, On 12/08/2019, 12:35, "George Dunlap" wrote: On 8/9/19 6:48 PM, Lars Kurth wrote: > Hi all, > > Following the discussion we had at the Developer Summit (see https://wiki.xenproject.org/wiki/Design_Sessions_2019#Community_Issues_.2F_Improveme

[Xen-devel] [RFC] Code of Conduct

Hi all, Following the discussion we had at the Developer Summit (see https://wiki.xenproject.org/wiki/Design_Sessions_2019#Community_Issues_.2F_Improvements_-_Communication.2C_Code_of_Conduct.2C_etc. for notes) I put together a draft for the Code of Conduct which can be found here as well as

[Xen-devel] [Xen-summit-2019] Design Session Notes

Hi all, I collated all the design session descriptions and all the notes I could find on xen-devel@ at https://wiki.xenproject.org/wiki/Design_Sessions_2019 I may be missing a few from day 1, as we lost some of the session in the system when we improvised the schedule to pack more sessions in

Re: [Xen-devel] [PATCH V2 6/6] iommu/arm: Add Renesas IPMMU-VMSA support

On 07/08/2019, 20:15, "Julien Grall" wrote: (+ Lars) Hi, On 8/7/19 5:01 PM, Oleksandr wrote: >>> + * you can found at: >>> + *url: >>> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git >>> + *branch: v4.14.75-ltsi/rcar-3.9.6

Re: [Xen-devel] [RFC] Re-working the patch submission guide

On 07/08/2019, 19:40, "Viktor Mitin" wrote: On Wed, Aug 7, 2019 at 9:04 PM Lars Kurth wrote: > > > On 05/08/2019, 18:49, "Lars Kurth" wrote: > > On 02/08/2019, 14:36, "Lars Kurth" wrote: > >

Re: [Xen-devel] [RFC] Re-working the patch submission guide

On 05/08/2019, 18:49, "Lars Kurth" wrote: On 02/08/2019, 14:36, "Lars Kurth" wrote: On 02/08/2019, 14:03, "Julien Grall" wrote: On 02/08/2019 14:02, Julien Gra

Re: [Xen-devel] [RFC] Re-working the patch submission guide

On 02/08/2019, 14:36, "Lars Kurth" wrote: On 02/08/2019, 14:03, "Julien Grall" wrote: On 02/08/2019 14:02, Julien Grall wrote: > Hi Jan, > > On 02/08/2019 13:52, Jan Beulich wrote:

Re: [Xen-devel] [RFC] Re-working the patch submission guide

On 02/08/2019, 14:03, "Julien Grall" wrote: On 02/08/2019 14:02, Julien Grall wrote: > Hi Jan, > > On 02/08/2019 13:52, Jan Beulich wrote: >> On 02.08.2019 13:14, Lars Kurth wrote: >>>> 1.5.4 Sending Patches Manually

[Xen-devel] [ANNOUNCE] Minutes of Aug 1 2019 Community Call

Hi all, please find attached the minutes of yesterday’s community call Also, at https://cryptpad.fr/pad/#/2/pad/view/MEmhAJP0tolLJOoFo1-ILwTDrKaz8xpWE+RljeHA5S4/ (read-only mode) Lars 2019-08 Community Call.pdf Description: 2019-08 Community Call.pdf

[Xen-devel] [RFC] Re-working the patch submission guide

Hi all, In preparation of migrating docs to sphinx-docs, I first wanted to clean up https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches. Before I do some work on it, I wanted to outline my thoughts on the content > 1 How To Generate and Submit Patches to the Xen Project > 1.1

Re: [Xen-devel] [PATCH v4 1/2] xen/arm: extend fdt_property_interrupts

> On 1 Aug 2019, at 15:02, Julien Grall wrote: > > Hi Lars, > > On 01/08/2019 14:59, Lars Kurth wrote: >>> On 1 Aug 2019, at 13:41, Julien Grall >> <mailto:julien.gr...@arm.com>> wrote: >>> >>> Hi Viktor, >>> >>

Re: [Xen-devel] [PATCH v4 1/2] xen/arm: extend fdt_property_interrupts

> On 1 Aug 2019, at 13:41, Julien Grall wrote: > > Hi Viktor, > > On 01/08/2019 13:26, Viktor Mitin wrote: >> Hi Julien and Volodymyr, >> On Wed, Jul 31, 2019 at 3:52 PM Julien Grall wrote: >>> >>> Hi, >>> > It is recommended (and probably required, but I can't find exact place >

Re: [Xen-devel] [PATCH] CODING_STYLE: clarify function argument indentation

> On 31 Jul 2019, at 17:54, Viktor Mitin wrote: > > Hi All, > > On Wed, Jul 31, 2019 at 7:45 PM Andrew Cooper > wrote: >> >> On 31/07/2019 17:24, Volodymyr Babchuk wrote: >>> There are coding style rules that are widely accepted by community, >>> but newer were formalized in the document.

Re: [Xen-devel] Xen Coding style and clang-format

> On 31 Jul 2019, at 12:43, Viktor Mitin wrote: > > On Wed, Jul 31, 2019 at 2:25 PM Julien Grall > wrote: >> >> >> >> On 31/07/2019 12:16, Viktor Mitin wrote: >>> On Mon, Jul 29, 2019 at 3:35 PM Julien Grall wrote: On 7/29/19 1:21 PM, Viktor Mitin wrote:

Re: [Xen-devel] [PATCH] Intel TXT: add reviewer, move to Odd Fixes state

> On 31 Jul 2019, at 12:52, Julien Grall wrote: > >> To move forward: >> * There should be a policy discussion > > How should I raise it? Do you want a patch again contribution-guidelines? I think we should start with an e-mail thread with an appropriate title on xen-devel@ (CCing

[Xen-devel] [ANNOUNCE} Call for agenda items for Aug 1st Community Call @ 15:00 UTC

Hi all, the proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/arfa2Pr3D2uIuEN3EWNTdOVT/ Alternatively, you can reply to this mail directly Agenda items appreciated by tomorrow Regards Lars P.S.: If you want to be added or removed from the CC list please reply privately == Dial-in

Re: [Xen-devel] [PATCH] Intel TXT: add reviewer, move to Odd Fixes state

> On 30 Jul 2019, at 11:08, George Dunlap wrote: > > On 7/30/19 10:54 AM, Julien Grall wrote: >> Hi Jan, >> >> On 30/07/2019 10:05, Jan Beulich wrote: >>> On 30.07.2019 10:54, Julien Grall wrote: On 7/30/19 9:29 AM, Jan Beulich wrote: > On 30.07.2019 08:56, Lukasz Hawrylko wrote:

Re: [Xen-devel] [RFC] XCP-ng subproject proposal

Hi everyone, adding committers, who would need to vote for or against the proposal. The title probably does not need an RFC, which is why no-one looked at it so far I think this is a great idea and I would want to welcome XCP-ng into the project: with this in mind, I vote +1 Lars > On 22

Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting

On 26/07/2019, 16:12, "Julien Grall" wrote: Hi Viktor, On 26/07/2019 15:58, Viktor Mitin wrote: > On Fri, Jul 19, 2019 at 11:37 AM Julien Grall wrote: >> >> Hi Tamas, >> >> On 18/07/2019 18:22, Tamas K Lengyel wrote: - Line 139: The { are

Re: [Xen-devel] [PATCH] tboot: remove maintainers and declare orphaned

> On 26 Jul 2019, at 08:17, Roger Pau Monné wrote: > > On Thu, Jul 25, 2019 at 03:08:07PM -0400, Rich Persaud wrote: >> (cc Intel and tboot-devel) >> >> Hi Roger, >> >> Thanks for your interest in documenting the status of maintenance for Intel >> TXT support in Xen. Intel TXT and Xen are

Re: [Xen-devel] Xen Coding style and clang-format

> On 26 Jul 2019, at 15:17, Viktor Mitin wrote: > > On Fri, Jul 26, 2019 at 4:52 PM Lars Kurth wrote: >>>> thank you for putting this mail together and driving this forward. I added >>>> committers@ as well as Doug. I am going to let others respond first.

Re: [Xen-devel] Xen Coding style and clang-format

> On 26 Jul 2019, at 14:45, Viktor Mitin wrote: > >> Hi Viktor, > > Hi Lars, > >> thank you for putting this mail together and driving this forward. I added >> committers@ as well as Doug. I am going to let others respond first. >> I am assuming we are looking for some testing? > > Yes,

Re: [Xen-devel] Xen Coding style and clang-format

> On 26 Jul 2019, at 13:30, Viktor Mitin wrote: > > Hi All, > > The Xen Project has a coding standard in place, but like many > projects, the standard is only enforced through peer review. Such > mistakes slip through and code is imported from other projects which > may not follow the same

Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting

On 19/07/2019, 14:50, "Rich Persaud" wrote: On Jul 19, 2019, at 09:31, Julien Grall wrote: >> On 19/07/2019 14:24, Julien Grall wrote: >> Hi Tamas, >>> On 19/07/2019 14:14, Tamas K Lengyel wrote: On Fri, Jul 19, 2019 at 7:11 AM Julien Grall wrote:

Re: [Xen-devel] Criteria / validation proposal: drop Xen

> On 12 Jul 2019, at 13:24, Peter Robinson wrote: > > On Fri, Jul 12, 2019 at 5:50 AM David Woodhouse wrote: >> >> >>> IIRC, what we have right now is a somewhat vague setup where we just >>> have 'local', 'ec2' and 'openstack' columns. The instructions for >>> "Amazon Web Services" just

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

On 26/06/2019, 18:44, "Stefano Stabellini" wrote: On Wed, 26 Jun 2019, Rich Persaud wrote: > > On Jun 26, 2019, at 06:45, Lars Kurth wrote: > > > > > > > > On 25/06/2019, 21:27, "Rich Persaud" wrote: > >

[Xen-devel] Xen Project Community Call Sign-up-sheet for future calls

Hi all, I have been using a probably a fairly old list of people to CC on mail related to community calls. If you received this mail and don’t want to be on the CC list, please remove your name and e-mail address from the list in https://cryptpad.fr/pad/#/2/pad/edit/D9vGzihPxxAOe6RFPz0sRCf+/

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

On 25/06/2019, 21:27, "Rich Persaud" wrote: > On Jun 25, 2019, at 16:17, Julien Grall wrote: > > Hi Rich, > > On 6/25/19 8:38 PM, Rich Persaud wrote: >>> On Jun 25, 2019, at 12:36, Lars Kurth wrote: >>> >>

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

Hi all: please add your agenda items. I had only ONE series which was highlighted as needing attention from others. Is this seriously the only one? Regards Lars On 21/06/2019, 16:45, "Lars Kurth" wrote: Hi all, Please propose topics by either editing the runn

Re: [Xen-devel] Migrating key developer docs to xen.git sphinx docs and refreshing them in the process

On 25/06/2019, 14:47, "Andrew Cooper" wrote: On 25/06/2019 13:15, Lars Kurth wrote: > On 25/06/2019, 10:03, "Julien Grall" wrote: > > >>> The point here is that we can be flexible and creative about the way to

Re: [Xen-devel] Migrating key developer docs to xen.git sphinx docs and refreshing them in the process

On 25/06/2019, 10:03, "Julien Grall" wrote: >>> The point here is that we can be flexible and creative about the way to >>> maintain the docs on xen.git. But as a technology is certainly better >>> than the wiki: we don't have to keep them all up-to-date with the code, >>> but

[Xen-devel] Migrating key developer docs to xen.git sphinx docs and refreshing them in the process

Hi all, since Andy created https://xenbits.xen.org/docs/sphinx-unstable/ and https://xenbits.xen.org/docs/sphinx-unstable-staging/ (sources in docs/hypervisor-guide, docs/guest-guide, docs/admin-guide) I was wondering whether it would not make sense to migrate some key documents in the wiki

[Xen-devel] Minimum Community Standards and Best Practice

Dear Community Members, at the 2017 Developer Summit the question of a Code of Conduct (CoC) for the Xen Project had come up and subsequently a number of individuals within the community have looked at the question of whether we should have a CoC or not. Note that there was a discussion at the

[Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

Hi all, Please propose topics by either editing the running agenda document at  https://cryptpad.fr/pad/#/2/pad/edit/V-JctV2vBlEnwliVLBlFLY7n/ or by replying to the mail. Note that currently I have * Nothing under: D) New Series / Series that need attention / Series that are important *

Re: [Xen-devel] [PATCH v3] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

> With this ... > > > Changes since v1 > > * Require a colon after repo:, file:, ... keywords > > * Replace manual:|auto: with file: as there auto: use-case was invalid > > * Added more verbose description of format

Re: [Xen-devel] [PATCH v3] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

more verbose description of format > > Changes since v2 > * Changed some formatting > * Removed examples > * Removed references to https ... move past the first --- separator ... > Signed-off-by: Lars Kurth Acked-by: Jan Beulich Are a

<    1   2   3   4   5   >