From: Andrii Anisov <andrii.anisov@gmail.com> To: Julien Grall <julien.grall@arm.com> Cc: Stefano Stabellini <sstabellini@kernel.org>, Andrii Anisov <andrii_anisov@epam.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com> Subject: Re: [PATCH RFC 2] [DO NOT APPLY] introduce VCPUOP_register_runstate_phys_memory_area hypercall Date: Tue, 28 May 2019 12:17:42 +0300 [thread overview] Message-ID: <d94e7186-5f5d-1d93-4462-af18ba7da018@gmail.com> (raw) In-Reply-To: <c31fb2f8-1703-61db-fd7d-f41db6a137d8@arm.com> Hello Julien, On 28.05.19 11:59, Julien Grall wrote: > I am not answering on the content yet, I will do that separately. The threading for this series looks quite confusing. The head of the thread is this patch (i.e RFC 2) but then you have a cover letter within the thread tagged "V3". Actually I've noticed the mangled threading. But not sure why it is so. I just passed a folder with those patches to git-send-mail. > From what I understand, the 2 e-mails tagged "V3" is the original version where as RFC 2 and RFC 3 are variants. Am I correct? Yes, sure. > If so, for next time, I would recommend to have the cover letter first and then all the patches send "In-Reply-To" the cover letter. This makes easier to track series. It might help. But before it worked well without additional tricks. -- Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrii Anisov <andrii.anisov@gmail.com> To: Julien Grall <julien.grall@arm.com> Cc: Stefano Stabellini <sstabellini@kernel.org>, Andrii Anisov <andrii_anisov@epam.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com> Subject: Re: [Xen-devel] [PATCH RFC 2] [DO NOT APPLY] introduce VCPUOP_register_runstate_phys_memory_area hypercall Date: Tue, 28 May 2019 12:17:42 +0300 [thread overview] Message-ID: <d94e7186-5f5d-1d93-4462-af18ba7da018@gmail.com> (raw) Message-ID: <20190528091742.6TO5BK6U2ue1nUsewIVJXKLtt2lLyRzQOY0ztqB3-Z8@z> (raw) In-Reply-To: <c31fb2f8-1703-61db-fd7d-f41db6a137d8@arm.com> Hello Julien, On 28.05.19 11:59, Julien Grall wrote: > I am not answering on the content yet, I will do that separately. The threading for this series looks quite confusing. The head of the thread is this patch (i.e RFC 2) but then you have a cover letter within the thread tagged "V3". Actually I've noticed the mangled threading. But not sure why it is so. I just passed a folder with those patches to git-send-mail. > From what I understand, the 2 e-mails tagged "V3" is the original version where as RFC 2 and RFC 3 are variants. Am I correct? Yes, sure. > If so, for next time, I would recommend to have the cover letter first and then all the patches send "In-Reply-To" the cover letter. This makes easier to track series. It might help. But before it worked well without additional tricks. -- Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-28 9:17 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-24 18:12 [PATCH RFC 2] [DO NOT APPLY] introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov 2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov 2019-05-24 18:12 ` [PATCH v3] Introduce runstate area registration with phys address Andrii Anisov 2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov 2019-05-24 18:12 ` [PATCH v3] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov 2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov 2019-06-07 14:23 ` Jan Beulich 2019-06-10 11:44 ` Julien Grall 2019-06-11 9:10 ` Jan Beulich 2019-06-11 10:22 ` Andrii Anisov 2019-06-11 12:12 ` Julien Grall 2019-06-11 12:26 ` Andrii Anisov 2019-06-11 12:32 ` Julien Grall 2019-06-11 12:40 ` Andrii Anisov 2019-06-13 12:21 ` Andrii Anisov 2019-06-13 12:39 ` Jan Beulich 2019-06-13 12:32 ` Andrii Anisov 2019-06-13 12:41 ` Jan Beulich 2019-06-13 12:48 ` Julien Grall 2019-06-13 12:58 ` Jan Beulich 2019-06-13 13:14 ` Julien Grall 2019-06-13 13:40 ` Jan Beulich 2019-06-13 14:41 ` Julien Grall 2019-06-14 14:36 ` Andrii Anisov 2019-06-14 14:39 ` Julien Grall 2019-06-14 15:11 ` Andrii Anisov 2019-06-14 15:24 ` Julien Grall 2019-06-14 16:11 ` Andrii Anisov 2019-06-14 16:20 ` Julien Grall 2019-06-14 16:25 ` Andrii Anisov 2019-06-17 6:27 ` Jan Beulich 2019-06-14 15:42 ` Jan Beulich 2019-06-14 16:23 ` Andrii Anisov 2019-06-17 6:28 ` Jan Beulich 2019-06-18 15:32 ` Andrii Anisov 2019-06-18 15:44 ` Jan Beulich 2019-06-11 16:09 ` Andrii Anisov 2019-06-12 7:27 ` Jan Beulich 2019-06-13 12:17 ` Andrii Anisov 2019-06-13 12:36 ` Jan Beulich 2019-06-11 16:13 ` Andrii Anisov 2019-05-24 18:12 ` [PATCH RFC 1] [DO NOT APPLY] " Andrii Anisov 2019-05-24 18:12 ` [Xen-devel] " Andrii Anisov 2019-05-28 8:59 ` [PATCH RFC 2] " Julien Grall 2019-05-28 8:59 ` [Xen-devel] " Julien Grall 2019-05-28 9:17 ` Andrii Anisov [this message] 2019-05-28 9:17 ` Andrii Anisov 2019-05-28 9:23 ` Julien Grall 2019-05-28 9:23 ` [Xen-devel] " Julien Grall 2019-05-28 9:36 ` Andrii Anisov 2019-05-28 9:36 ` [Xen-devel] " Andrii Anisov
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=d94e7186-5f5d-1d93-4462-af18ba7da018@gmail.com \ --to=andrii.anisov@gmail.com \ --cc=George.Dunlap@eu.citrix.com \ --cc=andrew.cooper3@citrix.com \ --cc=andrii_anisov@epam.com \ --cc=ian.jackson@eu.citrix.com \ --cc=jbeulich@suse.com \ --cc=julien.grall@arm.com \ --cc=konrad.wilk@oracle.com \ --cc=sstabellini@kernel.org \ --cc=tim@xen.org \ --cc=wei.liu2@citrix.com \ --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: linkBe 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).