From: Julien Grall <julien.grall@citrix.com>
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
"Ian Campbell (ian.campbell@citrix.com)"
<ian.campbell@citrix.com>
Subject: Re: [PATCH 0/2] xen: arm: Ensure all PTE bits have a known value
Date: Mon, 17 Aug 2015 11:23:57 -0700 [thread overview]
Message-ID: <55D226BD.3050702@citrix.com> (raw)
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7EC7CC@SJEXCHMB05.corp.ad.broadcom.com>
On 14/08/2015 14:41, Chris (Christopher) Brand wrote:
> Hi,
Hi Chris,
Thank you for the patch.
> This is more-or-less what Julien requested. He noted that pt.contig was never
> set to zero. When I looked further, I found other bits that were also never
> given a value. Looking at the callsites, they almost all seem to assume a value
> of zero, so that's what I went with.
>
> Patch 1 re-orders the assignments to match the declaration, making it clearer
> which ones are missing. Patch 2 then adds the missing bits.
>
> Chris
> P.S. Apologies for any threading issues - I have not yet managed to get git
> send-email working properly.
I'm usually using git format-patch to get a list of files (one per
patch) and my cover letter (--cover-letter).
Then I use git send-email *.patch which will send the patch correctly
threading.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-08-17 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 21:41 [PATCH 0/2] xen: arm: Ensure all PTE bits have a known value Chris (Christopher) Brand
2015-08-17 18:23 ` Julien Grall [this message]
2015-08-17 19:00 ` Chris (Christopher) Brand
-- strict thread matches above, loose matches on Subject: below --
2015-08-14 21:40 Chris (Christopher) Brand
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=55D226BD.3050702@citrix.com \
--to=julien.grall@citrix.com \
--cc=chris.brand@broadcom.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.