xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ben Sanda <Ben.Sanda@dornerworks.com>, Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 0/5] xentrace/xenalyze Support on ARM
Date: Wed, 6 Apr 2016 17:59:36 +0100	[thread overview]
Message-ID: <57054078.5060407@citrix.com> (raw)
In-Reply-To: <A2A949C387F3A54C9B4DAC2DCD2E9A85E333C729@Quimby.dw.local>

On 06/04/16 17:51, Ben Sanda wrote:
> Jan, 
>
>> A couple of formal things: This is v3, and I only now notice
>> indeed I should have looked at some of the patches. Yet which of them
>> isn't clear - I'm being Cc-ed on all of them, instead of just the ones
>> that submission guidelines say I should be. And then all patch
>> subjects start with xenalyze: or xentrace:, suggesting this series
>> isn't touching code other than those two. Generalization of
>> {get,put}_pg_owner(), otoh, while apparently a prereq for the
>> generalization of one or both of the two, should use a more indicative
>> component prefix (or maybe even none at all).
> Thank you for the comments, I will update the names of the patches so
> they are more obvious as to what they touch. As far as the CC'ing
> though, I'm not sure how to do this. When I create the patch and send
> it out  with git send-email I send one email for the entire patch set
> with one CC list. I don't know of a method to send a patch set but
> have each individual patch go to a different CC list.

Word your commit message like so:

Signed-off-by: $ME
---
CC: $SOMEONE
CC: $SOMEONE_ELSE

and `git send-email` will DTRT.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-04-06 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 18:48 [PATCH v3 0/5] xentrace/xenalyze Support on ARM Benjamin Sanda
2016-04-04 18:48 ` [PATCH v3 1/5] xentrace: Common Support for get_pg_owner/put_pg_owner on ARM and x86 Benjamin Sanda
2016-04-04 23:05   ` Andrew Cooper
2016-04-05  8:12   ` Jan Beulich
2016-04-14 19:59     ` Ben Sanda
2016-04-17  7:58       ` Jan Beulich
2016-04-04 18:48 ` [PATCH v3 2/5] xentrace: Memory/Page Mapping support for DOMID_XEN on ARM Benjamin Sanda
2016-04-08 10:42   ` Julien Grall
2016-04-08 15:49     ` Jan Beulich
2016-04-08 17:58       ` Andrew Cooper
2016-04-11  9:52         ` George Dunlap
2016-04-12 15:53           ` Julien Grall
2016-04-14 19:52             ` Ben Sanda
2016-04-20 12:48               ` Julien Grall
2016-04-22  9:42             ` Stefano Stabellini
2016-04-22 17:01               ` Julien Grall
2016-04-04 18:48 ` [PATCH v3 3/5] xentrace: Timestamp support for ARM platform Benjamin Sanda
2016-04-08 10:50   ` Julien Grall
2016-04-11 14:56   ` Konrad Rzeszutek Wilk
2016-04-04 18:48 ` [PATCH v3 4/5] xentrace: Trace Buffer Initialization on ARM Benjamin Sanda
2016-04-08 10:53   ` Julien Grall
2016-04-04 18:48 ` [PATCH v3 5/5] xenalyze: Build for Both ARM and x86 Platforms Benjamin Sanda
2016-04-05  8:09 ` [PATCH v3 0/5] xentrace/xenalyze Support on ARM Jan Beulich
2016-04-06 16:51   ` Ben Sanda
2016-04-06 16:59     ` Andrew Cooper [this message]
2016-04-06 17:03       ` Ben Sanda
2016-04-08 14:44   ` George Dunlap

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=57054078.5060407@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ben.Sanda@dornerworks.com \
    --cc=JBeulich@suse.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: 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;
as well as URLs for NNTP newsgroup(s).