From: "Jan Beulich" <jbeulich@suse.com>
To: julien.grall@arm.com
Cc: sstabellini@kernel.org, keir@xen.org, andre.przywara@arm.com,
ian.jackson@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [for-4.7 1/2] xen/bitops: Introduce macros to generate mask
Date: Wed, 20 Apr 2016 10:43:22 -0600 [thread overview]
Message-ID: <5717BFBA02000078000E6F44@prv-mh.provo.novell.com> (raw)
In-Reply-To: <57177785.20909@arm.com>
>>> Julien Grall <julien.grall@arm.com> 04/20/16 2:35 PM >>>
>It is a matter of taste.
Indeed.
> Is there any reason to not allow different way to create a mask?
I dislike it, but not so much to stand in the way to get it in. I.e. I'm not going
to NAK it, but I'm also not currently planning to ACK it.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-20 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 15:55 [for-4.7 0/2] xen/arm: traps: Correctly interpret the content of the register HPFAR_EL2 Julien Grall
2016-04-13 15:55 ` [for-4.7 1/2] xen/bitops: Introduce macros to generate mask Julien Grall
2016-04-13 18:07 ` Stefano Stabellini
2016-04-13 18:14 ` Andrew Cooper
2016-04-14 8:47 ` Julien Grall
2016-04-14 4:01 ` Jan Beulich
2016-04-14 8:55 ` Julien Grall
2016-04-14 14:56 ` Jan Beulich
2016-04-14 15:08 ` Julien Grall
2016-04-14 15:23 ` Jan Beulich
2016-04-20 12:35 ` Julien Grall
2016-04-20 16:43 ` Jan Beulich [this message]
2016-04-22 11:33 ` Julien Grall
2016-04-22 11:49 ` Stefano Stabellini
2016-04-22 15:33 ` Julien Grall
2016-04-22 15:42 ` Stefano Stabellini
2016-04-13 15:55 ` [for-4.7 2/2] xen/arm: traps: Correctly interpret the content of the register HPFAR_EL2 Julien Grall
2016-04-13 18:17 ` Stefano Stabellini
2016-04-13 19:11 ` Tamas K Lengyel
2016-04-13 20:33 ` André Przywara
2016-04-14 17:47 ` [for-4.7 0/2] " Wei Liu
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=5717BFBA02000078000E6F44@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andre.przywara@arm.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=keir@xen.org \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).