From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, bp@alien8.de,
hpa@zytor.com, boris.ostrovsky@oracle.com, jgross@suse.com,
sstabellini@kernel.org, peterz@infradead.org,
srinivas.eeda@oracle.com
Subject: Re: [PATCH v2 0/7] misc fixes to PV extentions code
Date: Thu, 27 Jun 2019 16:47:11 +0800 [thread overview]
Message-ID: <ab80e007-1d7e-ff13-d11a-10999d198ad3@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906261511180.32342@nanos.tec.linutronix.de>
On 2019/6/26 21:39, Thomas Gleixner wrote:
> Documentation/process/submitting-patches.rst clearly explains why it is a
> bad idea to send random collections of patches especially if some patches
> are independent and contain bug fixes.
>
> These rules exist for a reason and are not subject to personal
> interpretation. You want your patches to be reviewed and merged, so pretty
> please make the life of those who need to do that as easy as possible.
>
> It's not the job of reviewers and maintainers to distangle your randomly
> ordered patch series.
Ok，understood. I'll send independent and unrelated patch seperately.
Thanks
Zhenzhong
next prev parent reply other threads:[~2019-06-27 8:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 12:02 Zhenzhong Duan
2019-06-24 12:02 ` [PATCH v2 1/7] x86/xen: Mark xen_hvm_need_lapic() and xen_hvm_need_lapic() as __init Zhenzhong Duan
2019-06-24 12:02 ` [PATCH v2 2/7] x86/jailhouse: Mark jailhouse_x2apic_available " Zhenzhong Duan
2019-06-24 12:02 ` [PATCH v2 3/7] x86: Add nopv parameter to disable PV extensions Zhenzhong Duan
2019-06-26 9:38 ` Juergen Gross
2019-06-24 12:02 ` [PATCH v2 4/7] Revert "xen: Introduce 'xen_nopv' to disable PV extensions for HVM guests." Zhenzhong Duan
2019-06-26 9:39 ` Juergen Gross
2019-06-26 13:48 ` Thomas Gleixner
2019-06-24 12:02 ` [PATCH v2 5/7] x86/xen: nopv parameter support for HVM guest Zhenzhong Duan
2019-06-25 12:31 ` Juergen Gross
2019-06-26 8:56 ` Zhenzhong Duan
2019-06-26 9:03 ` Juergen Gross
2019-06-24 12:02 ` [PATCH v2 6/7] locking/spinlocks, paravirt, hyperv: Correct the hv_nopvspin case Zhenzhong Duan
2019-06-27 22:28 ` Sasha Levin
2019-06-28 0:53 ` Zhenzhong Duan
2019-06-24 12:02 ` [PATCH v2 7/7] Revert "x86/paravirt: Set up the virt_spin_lock_key after static keys get initialized" Zhenzhong Duan
2019-06-26 13:39 ` [PATCH v2 0/7] misc fixes to PV extentions code Thomas Gleixner
2019-06-27 8:47 ` Zhenzhong Duan [this message]
2019-06-27 12:24 ` Thomas Gleixner
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=ab80e007-1d7e-ff13-d11a-10999d198ad3@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srinivas.eeda@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®