[Xen-devel] [TESTDAY] Test report (salvator-x)

2017-10-28 Thread Iurii Artemenko
* Hardware: Salvator-X board with Renesas R-Car H3 SoC (ARM64) * Software: XEN 4.10-rc0 System based on Renesas Yocto 2.19.0 BSP [1] Linux kernel 4.9 * Guest operating systems: The same system as dom0. * Functionality tested: xl create/reboot/shutdown Guest domain reboot from its console *

Re: [Xen-devel] Xen checkpatch infrastructure design

2017-07-26 Thread Iurii Artemenko
Hi Lars, > I was wondering how you deal with the gaps. I suppose these gaps could > possibly be covered in clang-format-diff.py > Of course this info may be out-of-date I assumed that everything is fine with clang-format and started with python script. Now I have checked both

Re: [Xen-devel] Xen checkpatch infrastructure design

2017-07-26 Thread Iurii Artemenko
Hello, Juergen > How does this work for a patch which is perfectly fine, while not > touched parts of the patched file are not? The tool should only > look at the added lines, not at those left unmodified. The tool looks at touched lines only since it works with unified diff and parse it. As

Re: [Xen-devel] Xen checkpatch infrastructure design

2017-07-24 Thread Iurii Artemenko
Hello Juergen, I've started to work on checkpatch-like python script. I make it based on clang-format-diff.py and it works as pre-commit hook. > The easiest way to accomplish that is a file in the repository's root > directory containing the necessary information. It will be named > "STYLES"