From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 0/4] add support for vNVDIMM Date: Wed, 6 Jan 2016 15:37:51 +0000 Message-ID: <1452094671.21055.85.camel@citrix.com> References: <1451388711-18646-1-git-send-email-haozhong.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1451388711-18646-1-git-send-email-haozhong.zhang@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Haozhong Zhang , xen-devel@lists.xen.org Cc: Kevin Tian , Wei Liu , Jun Nakajima , Stefano Stabellini , Andrew Cooper , Ian Jackson , Jan Beulich , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Tue, 2015-12-29 at 19:31 +0800, Haozhong Zhang wrote: > This patch series is the Xen part patch to provide virtual NVDIMM to > guest. The corresponding QEMU patch series is sent separately with the > title "[PATCH 0/2] add vNVDIMM support for Xen". When you send multiple related series like this please could you tag them in the 0/N subject line somehow as to the tree they are for. Either tagging with "[PATCH XEN 0/4]" (via git send-email --subject-prefix="PATCH XEN") or using something like "xen: add support for ..." (and the equivalent for other trees). In this case I incorrectly categorised this based on the subject as a repost of a QEMU series I had seen just before and hence ignored it. I spotted a bit of diffstat in a reply and have now put it into my queue to look at, but that was pure luck. Ian.