1 2 List of maintainers and how to submit changes 3 ============================================= 4 5Please try to follow the guidelines below. This will make things 6easier on the maintainers. Not all of these guidelines matter for every 7trivial patch so apply some common sense. 8 91. Always _test_ your changes, however small, on at least 4 or 10 5 people, preferably many more. 11 122. Make sure your changes compile correctly in multiple 13 configurations. For example, both 32- and 64-bit x86. 14 153. Make a patch available to the relevant maintainer in the list. Use 16 'diff -u' to make the patch easy to merge. Be prepared to get your 17 changes sent back with seemingly silly requests about formatting 18 and variable names. These aren't as silly as they seem. One 19 job the maintainers do is to keep things looking the same. 20 21 PLEASE see https://wiki.xenproject.org/wiki/Submitting_Xen_Patches for 22 hints on how to submit a patch to xen-unstable in a suitable 23 form. 24 25 PLEASE try to include any credit lines you want added with the 26 patch. It avoids people being missed off by mistake and makes 27 it easier to know who wants adding and who doesn't. 28 29 PLEASE document known bugs. If it doesn't work for everything 30 or does something very odd once a month document it. 31 32 PLEASE remember that submissions must be made under the terms 33 of the "Developer's Certificate of Origin" (DCO) and should include 34 a Signed-off-by: line. 35 364. Make sure you have the right to send any changes you make. If you 37 do changes at work you may find your employer owns the patch 38 not you. 39 405. Happy hacking. 41 42 43 Stable Release Maintenance 44 ========================== 45 46The policy for inclusion in a Xen stable release is different to that 47for inclusion in xen-unstable. 48 49Please see https://wiki.xenproject.org/wiki/Xen_Maintenance_Releases for more 50information. 51 52Backport requests should be made on the xen-devel@lists.xenproject.org 53list. Remember to copy the appropriate stable branch maintainer who 54will be listed in this section of the MAINTAINERS file in the 55appropriate branch. 56 57 Unstable Subsystem Maintainers 58 ============================== 59 60Descriptions of section entries: 61 62 M: Maintainer: FullName <address@domain> 63 Maintainers should be CCed on patches. At least one of them 64 needs to approve changes to the covered files. 65 R: Designated reviewer: FullName <address@domain> 66 Reviewers should be CCed on patches. However, they do not 67 have a formal governance role, and are listed here 68 simply because of their own request. 69 L: Mailing list that is relevant to this area 70 W: Web-page with status/info 71 T: SCM tree type and location. Type is one of: git, hg, quilt, stgit. 72 S: Status, one of the following: 73 Supported: Someone is actually paid to look after this. 74 Maintained: Someone actually looks after it. 75 Odd Fixes: It has a maintainer but they don't have time to do 76 much other than throw the odd patch in. See below.. 77 Orphan: No current maintainer [but maybe you could take the 78 role as you write your new code]. 79 Obsolete: Old code. Something tagged obsolete generally means 80 it has been replaced by a better system and you 81 should be using that. 82 F: Files and directories with wildcard patterns. 83 A trailing slash includes all files and subdirectory files. 84 F: drivers/net/ all files in and below drivers/net 85 F: drivers/net/* all files in drivers/net, but not below 86 F: */net/* all files in "any top level directory"/net 87 One pattern per line. Multiple F: lines acceptable. 88 X: Files and directories that are NOT maintained, same rules as F: 89 Files exclusions are tested before file matches. 90 Can be useful for excluding a specific subdirectory, for instance: 91 F: net/ 92 X: net/ipv6/ 93 matches all files in and below net excluding net/ipv6/ 94 K: Keyword perl extended regex pattern to match content in a 95 patch or file. For instance: 96 K: of_get_profile 97 matches patches or files that contain "of_get_profile" 98 K: \b(printk|pr_(info|err))\b 99 matches patches or files that contain one or more of the words 100 printk, pr_info or pr_err 101 One regex pattern per line. Multiple K: lines acceptable. 102 V: Version identifier that must be under THE REST and follows 103 the format: 104 xen-maintainers-<version format number of this file> 105 106 107 Check-in policy 108 =============== 109 110In order for a patch to be checked in, in general, several conditions 111must be met: 112 1131. In order to get a change to a given file committed, it must have 114 the approval of at least one maintainer of that file. 115 116 A patch of course needs Acks from the maintainers of each file that 117 it changes; so a patch which changes xen/arch/x86/traps.c, 118 xen/arch/x86/mm/p2m.c, and xen/arch/x86/mm/shadow/multi.c would 119 require an Ack from each of the three sets of maintainers. 120 121 See below for rules on nested maintainership. 122 1232. Each change must have appropriate approval from someone other than 124 the person who wrote it. This can be either: 125 126 a. An Acked-by from a maintainer of the code being touched (a 127 co-maintainer if available, or a more general level maintainer if 128 not available; see the secton on nested maintainership) 129 130 b. A Reviewed-by by anyone of suitable stature in the community 131 1323. Sufficient time must have been given for anyone to respond. This 133 depends in large part upon the urgency and nature of the patch. 134 For a straightforward uncontroversial patch, a day or two may be 135 sufficient; for a controversial patch, a week or two may be better. 136 1374. There must be no "open" objections. 138 139In a case where one person submits a patch and a maintainer gives an 140Ack, the Ack stands in for both the approval requirement (#1) and the 141Acked-by-non-submitter requirement (#2). 142 143In a case where a maintainer themselves submits a patch, the 144Signed-off-by meets the approval requirement (#1); so a Review 145from anyone in the community suffices for requirement #2. 146 147Before a maintainer checks in their own patch with another community 148member's R-b but no co-maintainer Ack, it is especially important to 149give their co-maintainer opportunity to give feedback, perhaps 150declaring their intention to check it in without their co-maintainers 151ack a day before doing so. 152 153In the case where two people collaborate on a patch, at least one of 154whom is a maintainer -- typically where one maintainer will do an 155early version of the patch, and another maintainer will pick it up and 156revise it -- there should be two Signed-off-by's and one Acked-by or 157Reviewed-by; with the maintainer who did the most recent change 158sending the patch, and an Acked-by or Reviewed-by coming from the 159maintainer who did not most recently edit the patch. This satisfies 160the requirement #2 because a) the Signed-off-by of the sender approves 161the final version of the patch; including all parts of the patch that 162the sender did not write b) the Reviewed-by approves the final version 163of the patch, including all patches that the reviewer did not write. 164Thus all code in the patch has been approved by someone who did not 165write it. 166 167Maintainers may choose to override non-maintainer objections in the 168case that consensus can't be reached. 169 170As always, no policy can cover all possible situations. In 171exceptional circumstances, committers may commit a patch in absence of 172one or more of the above requirements, if they are reasonably 173confident that the other maintainers will approve of their decision in 174retrospect. 175 176 The meaning of nesting 177 ====================== 178 179Many maintainership areas are "nested": for example, there are entries 180for xen/arch/x86 as well as xen/arch/x86/mm, and even 181xen/arch/x86/mm/shadow; and there is a section at the end called "THE 182REST" which lists all committers. The meaning of nesting is that: 183 1841. Under normal circumstances, the Ack of the most specific maintainer 185is both necessary and sufficient to get a change to a given file 186committed. So a change to xen/arch/x86/mm/shadow/multi.c requires the 187the Ack of the xen/arch/x86/mm/shadow maintainer for that part of the 188patch, but would not require the Ack of the xen/arch/x86 maintainer or 189the xen/arch/x86/mm maintainer. 190 1912. In unusual circumstances, a more general maintainer's Ack can stand 192in for or even overrule a specific maintainer's Ack. Unusual 193circumstances might include: 194 - The patch is fixing a high-priority issue causing immediate pain, 195 and the more specific maintainer is not available. 196 - The more specific maintainer has not responded either to the 197 original patch, nor to "pings", within a reasonable amount of time. 198 - The more general maintainer wants to overrule the more specific 199 maintainer on some issue. (This should be exceptional.) 200 - In the case of a disagreement between maintainers, THE REST can 201 settle the matter by majority vote. (This should be very exceptional 202 indeed.) 203 204 205Maintainers List (try to look for most precise areas first) 206 207 ----------------------------------- 208 2099PFSD 210M: Juergen Gross <jgross@suse.com> 211M: Anthony PERARD <anthony.perard@vates.tech> 212S: Supported 213F: tools/9pfsd/ 214 215ACPI 216M: Jan Beulich <jbeulich@suse.com> 217S: Supported 218F: xen/arch/x86/acpi/ 219F: xen/drivers/acpi/ 220F: xen/include/acpi/ 221F: tools/libacpi/ 222 223ARGO 224M: Christopher Clark <christopher.w.clark@gmail.com> 225S: Maintained 226F: xen/include/public/argo.h 227F: xen/include/xen/argo.h 228F: xen/common/argo.c 229 230ARINC653 SCHEDULER 231M: Nathan Studer <nathan.studer@dornerworks.com> 232M: Stewart Hildebrand <stewart@stew.dk> 233S: Supported 234L: xen-devel@dornerworks.com 235F: xen/common/sched/arinc653.c 236F: tools/libs/ctrl/xc_arinc653.c 237 238ARM (W/ VIRTUALISATION EXTENSIONS) ARCHITECTURE 239M: Stefano Stabellini <sstabellini@kernel.org> 240M: Julien Grall <julien@xen.org> 241M: Bertrand Marquis <bertrand.marquis@arm.com> 242M: Michal Orzel <michal.orzel@amd.com> 243R: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com> 244S: Supported 245L: xen-devel@lists.xenproject.org 246F: docs/misc/arm/ 247F: xen/arch/arm/ 248F: xen/drivers/char/arm-uart.c 249F: xen/drivers/char/cadence-uart.c 250F: xen/drivers/char/exynos4210-uart.c 251F: xen/drivers/char/imx-lpuart.c 252F: xen/drivers/char/meson-uart.c 253F: xen/drivers/char/mvebu-uart.c 254F: xen/drivers/char/omap-uart.c 255F: xen/drivers/char/pl011.c 256F: xen/drivers/char/scif-uart.c 257F: xen/drivers/passthrough/arm/ 258F: xen/include/public/arch-arm/ 259F: xen/include/public/arch-arm.h 260 261ARM SMMU 262M: Julien Grall <julien@xen.org> 263M: Rahul Singh <rahul.singh@arm.com> 264S: Supported 265F: xen/drivers/passthrough/arm/smmu.c 266 267ARM SMMUv3 268M: Bertrand Marquis <bertrand.marquis@arm.com> 269M: Rahul Singh <rahul.singh@arm.com> 270S: Supported 271F: xen/drivers/passthrough/arm/smmu-v3.c 272 273Change Log 274M: Oleksii Kurochko <oleksii.kurochko@gmail.com> 275R: Community Manager <community.manager@xenproject.org> 276S: Maintained 277F: CHANGELOG.md 278 279Continuous Integration (CI) 280M: Doug Goldstein <cardoe@cardoe.com> 281M: Stefano Stabellini <sstabellini@kernel.org> 282W: https://gitlab.com/xen-project/xen 283S: Supported 284F: .gitlab-ci.yml 285F: automation/ 286 287CPU POOLS 288M: Juergen Gross <jgross@suse.com> 289M: Dario Faggioli <dfaggioli@suse.com> 290S: Supported 291F: xen/common/sched/*cpupool.c 292 293DEVICE TREE 294M: Stefano Stabellini <sstabellini@kernel.org> 295M: Julien Grall <julien@xen.org> 296S: Supported 297F: xen/common/libfdt/ 298F: xen/common/device_tree.c 299F: xen/common/dt-overlay.c 300F: xen/include/xen/libfdt/ 301F: xen/include/xen/device_tree.h 302F: xen/drivers/passthrough/device_tree.c 303 304ECLAIR 305R: Simone Ballarin <simone.ballarin@bugseng.com> 306S: Supported 307F: automation/eclair_analysis/ 308F: automation/scripts/eclair 309 310EFI 311M: Daniel P. Smith <dpsmith@apertussolutions.com> 312M: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> 313R: Jan Beulich <jbeulich@suse.com> 314S: Supported 315F: xen/arch/x86/efi/ 316F: xen/arch/x86/include/asm/efi*.h 317F: xen/arch/x86/include/asm/x86_*/efi*.h 318F: xen/common/efi/ 319F: xen/include/efi/ 320 321GDBSX DEBUGGER 322M: Elena Ufimtseva <elena.ufimtseva@oracle.com> 323S: Supported 324F: xen/arch/x86/debug.c 325F: tools/debugger/gdbsx/ 326 327GOLANG BINDINGS 328M: Nick Rosbrook <rosbrookn@gmail.com> 329R: George Dunlap <gwd@xenproject.org> 330S: Maintained 331F: tools/golang 332 333HYPFS 334M: Juergen Gross <jgross@suse.com> 335S: Supported 336F: tools/include/xenhypfs.h 337F: tools/libs/hypfs/ 338F: tools/misc/xenhypfs.c 339F: xen/common/hypfs.c 340F: xen/include/xen/hypfs.h 341 342IMX8QM/QXP SUPPORT 343R: John Ernberg <john.ernberg@actia.se> 344F: xen/arch/arm/platforms/imx8qm.c 345F: xen/drivers/char/imx-lpuart.c 346 347INTEL(R) TRUSTED EXECUTION TECHNOLOGY (TXT) 348R: Lukasz Hawrylko <lukasz@hawrylko.pl> 349R: Daniel P. Smith <dpsmith@apertussolutions.com> 350R: Mateusz Mówka <mateusz.mowka@intel.com> 351S: Odd Fixes 352F: xen/arch/x86/include/asm/tboot.h 353F: xen/arch/x86/tboot.c 354 355IOMMU VENDOR INDEPENDENT CODE 356M: Jan Beulich <jbeulich@suse.com> 357R: Roger Pau Monné <roger.pau@citrix.com> 358S: Supported 359F: xen/drivers/passthrough/ 360X: xen/drivers/passthrough/amd/ 361X: xen/drivers/passthrough/arm/ 362X: xen/drivers/passthrough/vtd/ 363X: xen/drivers/passthrough/device_tree.c 364F: xen/include/xen/iommu.h 365 366KCONFIG 367M: Doug Goldstein <cardoe@cardoe.com> 368S: Supported 369F: docs/misc/kconfig{,-language}.txt 370F: xen/tools/kconfig/ 371 372KDD DEBUGGER 373M: Tim Deegan <tim@xen.org> 374S: Odd Fixes 375F: tools/debugger/kdd/ 376 377KEXEC 378M: Andrew Cooper <andrew.cooper3@citrix.com> 379S: Supported 380F: xen/common/{kexec,kimage}.c 381F: xen/include/xen/{kexec,kimage}.h 382F: xen/arch/x86/machine_kexec.c 383F: xen/arch/x86/x86_64/kexec_reloc.S 384 385LIBS 386M: Anthony PERARD <anthony.perard@vates.tech> 387R: Juergen Gross <jgross@suse.com> 388S: Supported 389F: tools/include/libxenvchan.h 390F: tools/include/libxl*.h 391F: tools/include/xencall.h 392F: tools/include/xenctrl*.h 393F: tools/include/xendevicemodel.h 394F: tools/include/xenevtchn.h 395F: tools/include/xenforeignmemory.h 396F: tools/include/xengnttab.h 397F: tools/include/xenguest.h 398F: tools/include/xenhypfs.h 399F: tools/include/xenstat.h 400F: tools/include/xentoolcore*.h 401F: tools/include/xentoollog.h 402F: tools/libs/ 403 404LIVEPATCH 405M: Roger Pau Monné <roger.pau@citrix.com> 406M: Ross Lagerwall <ross.lagerwall@citrix.com> 407S: Supported 408F: docs/misc/livepatch.pandoc 409F: tools/misc/xen-livepatch.c 410F: xen/arch/*/include/asm/livepatch.h 411F: xen/arch/*/livepatch* 412F: xen/arch/*/*/livepatch* 413F: xen/common/livepatch* 414F: xen/include/xen/livepatch* 415F: xen/test/livepatch/* 416 417MINI-OS 418M: Samuel Thibault <samuel.thibault@ens-lyon.org> 419M: Juergen Gross <jgross@suse.com> 420S: Supported 421L: minios-devel@lists.xenproject.org 422T: git https://xenbits.xenproject.org/git-http/mini-os.git 423F: config/MiniOS.mk 424 425OCAML TOOLS 426M: Christian Lindig <christian.lindig@citrix.com> 427M: David Scott <dave@recoil.org> 428S: Supported 429F: tools/ocaml/ 430 431OVMF UPSTREAM 432M: Anthony PERARD <anthony.perard@vates.tech> 433S: Supported 434T: git https://xenbits.xenproject.org/git-http/ovmf.git 435 436POWER MANAGEMENT 437M: Jan Beulich <jbeulich@suse.com> 438S: Supported 439F: xen/arch/x86/acpi/ 440X: xen/arch/x86/acpi/boot.c 441X: xen/arch/x86/acpi/lib.c 442F: xen/drivers/cpufreq/ 443F: xen/include/acpi/cpufreq/ 444 445PPC64 446M: Shawn Anastasio <sanastasio@raptorengineering.com> 447F: xen/arch/ppc/ 448 449PUBLIC I/O INTERFACES AND PV DRIVERS DESIGNS 450M: Juergen Gross <jgross@suse.com> 451S: Supported 452F: xen/include/public/io/ 453 454PYTHON BINDINGS 455M: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> 456S: Supported 457F: tools/python 458 459QEMU-DM 460S: Supported 461T: git https://xenbits.xenproject.org/git-http/qemu-xen-traditional.git 462 463QEMU UPSTREAM 464M: Stefano Stabellini <sstabellini@kernel.org> 465M: Anthony Perard <anthony.perard@vates.tech> 466S: Supported 467T: git https://xenbits.xenproject.org/git-http/qemu-xen.git 468 469REMUS 470S: Orphan 471F: docs/README.remus 472F: tools/libs/light/libxl_remus_* 473F: tools/libs/light/libxl_netbuffer.c 474F: tools/libs/light/libxl_nonetbuffer.c 475F: tools/hotplug/Linux/remus-netbuf-setup 476F: tools/hotplug/Linux/block-drbd-probe 477 478RISCV 479R: Alistair Francis <alistair.francis@wdc.com> 480R: Bob Eshleman <bobbyeshleman@gmail.com> 481R: Connor Davis <connojdavis@gmail.com> 482S: Supported 483F: config/riscv64.mk 484F: xen/arch/riscv/ 485 486RTDS SCHEDULER 487M: Dario Faggioli <dfaggioli@suse.com> 488M: Meng Xu <mengxu@cis.upenn.edu> 489S: Supported 490F: xen/common/sched/rt.c 491 492SCHEDULING 493M: Dario Faggioli <dfaggioli@suse.com> 494M: Juergen Gross <jgross@suse.com> 495R: George Dunlap <gwd@xenproject.org> 496S: Supported 497F: xen/common/sched/ 498 499SEABIOS UPSTREAM 500M: Wei Liu <wl@xen.org> 501S: Supported 502T: git https://xenbits.xenproject.org/git-http/seabios.git 503 504STUB DOMAINS 505M: Samuel Thibault <samuel.thibault@ens-lyon.org> 506S: Supported 507F: config/Stubdom.mk.in 508F: m4/stubdom.m4 509F: stubdom/ 510 511TEE MEDIATORS 512M: Volodymyr Babchuk <volodymyr_babchuk@epam.com> 513S: Supported 514F: xen/arch/arm/include/asm/tee 515F: xen/arch/arm/tee/ 516 517TOOLSTACK 518M: Anthony PERARD <anthony.perard@vates.tech> 519S: Supported 520F: autogen.sh 521F: config/*.in 522F: install.sh 523F: m4/ 524F: configure 525F: docs/Makefile 526F: docs/man/ 527F: stubdom/Makefile 528F: *.ac 529F: */configure 530F: */*.ac 531F: tools/ 532 533VM EVENT, MEM ACCESS and MONITOR 534M: Tamas K Lengyel <tamas@tklengyel.com> 535R: Alexandru Isaila <aisaila@bitdefender.com> 536R: Petre Pircalabu <ppircalabu@bitdefender.com> 537S: Supported 538F: tools/misc/xen-access.c 539F: xen/arch/*/*/mem_access.c 540F: xen/arch/*/*/monitor.c 541F: xen/arch/*/*/vm_event.c 542F: xen/arch/*/include/asm/*/mem_access.h 543F: xen/arch/*/include/asm/*/monitor.h 544F: xen/arch/*/include/asm/*/vm_event.h 545F: xen/arch/*/include/asm/mem_access.h 546F: xen/arch/*/include/asm/monitor.h 547F: xen/arch/*/include/asm/vm_event.h 548F: xen/arch/*/mem_access.c 549F: xen/arch/*/monitor.c 550F: xen/arch/*/vm_event.c 551F: xen/common/mem_access.c 552F: xen/common/monitor.c 553F: xen/common/vm_event.c 554F: xen/include/*/mem_access.h 555F: xen/include/*/monitor.h 556F: xen/include/*/vm_event.h 557 558VPCI 559M: Roger Pau Monné <roger.pau@citrix.com> 560S: Supported 561F: tools/tests/vpci/ 562F: xen/drivers/vpci/ 563F: xen/include/xen/vpci.h 564 565VTPM 566M: Daniel De Graaf <dgdegra@tycho.nsa.gov> 567M: Quan Xu <quan.xu0@gmail.com> 568S: Supported 569F: extras/mini-os/tpm* 570F: extras/mini-os/include/tpm* 571F: stubdom/vtpm/ 572F: stubdom/vtpmmgr/ 573F: docs/misc/vtpm-platforms.txt 574 575X86 ARCHITECTURE 576M: Jan Beulich <jbeulich@suse.com> 577M: Andrew Cooper <andrew.cooper3@citrix.com> 578M: Roger Pau Monné <roger.pau@citrix.com> 579S: Supported 580L: xen-devel@lists.xenproject.org 581F: xen/arch/x86/ 582F: xen/drivers/passthrough/amd/ 583F: xen/drivers/passthrough/vtd/ 584F: xen/include/public/arch-x86/ 585F: xen/include/xen/lib/x86/ 586F: xen/lib/x86/ 587F: xen/tools/gen-cpuid.py 588F: tools/firmware/hvmloader/ 589F: tools/firmware/rombios/ 590F: tools/firmware/vgabios/ 591F: tools/fuzz/cpu-policy/ 592F: tools/fuzz/x86_instruction_emulator/ 593F: tools/misc/xen-cpuid.c 594F: tools/tests/cpu-policy/ 595F: tools/tests/x86_emulator/ 596 597X86 MEMORY MANAGEMENT 598M: Jan Beulich <jbeulich@suse.com> 599M: Andrew Cooper <andrew.cooper3@citrix.com> 600S: Supported 601F: xen/arch/x86/mm/ 602 603X86 MEMORY PAGING 604S: Orphaned 605F: xen/arch/x86/mm/mem_paging.c 606 607X86 MEMORY SHARING 608M: Tamas K Lengyel <tamas@tklengyel.com> 609S: Odd Fixes 610F: xen/arch/x86/mm/mem_sharing.c 611F: tools/tests/mem-sharing/ 612 613X86 SHADOW PAGETABLES 614M: Jan Beulich <jbeulich@suse.com> 615M: Andrew Cooper <andrew.cooper3@citrix.com> 616R: Tim Deegan <tim@xen.org> 617S: Maintained 618F: xen/arch/x86/mm/shadow/ 619 620X86 VIRIDIAN ENLIGHTENMENTS 621M: Paul Durrant <paul@xen.org> 622S: Supported 623F: xen/arch/x86/guest/hyperv/ 624F: xen/arch/x86/hvm/viridian/ 625F: xen/arch/x86/include/asm/guest/hyperv.h 626F: xen/arch/x86/include/asm/guest/hyperv-hcall.h 627F: xen/arch/x86/include/asm/guest/hyperv-tlfs.h 628F: xen/arch/x86/include/asm/hvm/viridian.h 629 630XENSTORE 631M: Juergen Gross <jgross@suse.com> 632R: Julien Grall <julien@xen.org> 633S: Supported 634F: tools/helpers/init-xenstore-domain.c 635F: tools/include/xenstore-compat/ 636F: tools/include/xenstore.h 637F: tools/include/xenstore_lib.h 638F: tools/include/xen-tools/xenstore-common.h 639F: tools/libs/store/ 640F: tools/xenstored/ 641F: tools/xs-clients/ 642 643XEN MISRA ANALYSIS TOOLS 644M: Luca Fancellu <luca.fancellu@arm.com> 645S: Supported 646F: xen/scripts/xen_analysis/ 647F: xen/scripts/xen-analysis.py 648F: xen/scripts/diff-report.py 649F: xen/tools/cppcheck-plat/ 650F: xen/tools/convert_misra_doc.py 651F: xen/tools/cppcheck-cc.sh 652 653XSM/FLASK 654M: Daniel P. Smith <dpsmith@apertussolutions.com> 655S: Supported 656F: tools/flask/ 657F: xen/include/xsm/ 658F: xen/xsm/ 659F: docs/misc/xsm-flask.txt 660K: xsm_.* 661K: \b(xsm|XSM)\b 662 663THE REST 664M: Andrew Cooper <andrew.cooper3@citrix.com> 665M: Jan Beulich <jbeulich@suse.com> 666M: Julien Grall <julien@xen.org> 667M: Stefano Stabellini <sstabellini@kernel.org> 668L: xen-devel@lists.xenproject.org 669S: Supported 670F: * 671F: */ 672V: xen-maintainers-1 673