From: "Zhang, Jonathan Zhixiong" <zjzhang@codeaurora.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
rjw@rjwysocki.net, lenb@kernel.org, ying.huang@intel.com,
leif.lindholm@linaro.org, al.stone@linaro.org, fu.wei@linaro.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linaro-acpi@lists.linaro.org,
vgandhi@codeaurora.org, Tony Luck <tony.luck@gmail.com>
Subject: Re: [PATCH V2 3/3] acpi, apei: use EFI memmap to map GHES memory
Date: Fri, 05 Jun 2015 10:06:57 -0700 [thread overview]
Message-ID: <5571D731.4000809@codeaurora.org> (raw)
In-Reply-To: <20150605165045.GL3679@pd.tnic>
On 6/5/2015 9:50 AM, Borislav Petkov wrote:
> On Fri, Jun 05, 2015 at 09:43:26AM -0700, Zhang, Jonathan Zhixiong wrote:
>> Thanks Matt for the review. Yes, you are right on, I am following
>> this:
>>> modify ghes_ioremap_* to query the EFI memmap (if
>>> it's available at runtime) to lookup the correct mapping attributes.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> So please do not top-post.
>
> Thanks.
>
Will do. Thanks for the advise, Borislav.
--
Jonathan (Zhixiong) Zhang
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-06-05 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 19:12 [PATCH V2 0/3] map GHES memory region with EFI memory map Jonathan (Zhixiong) Zhang
2015-06-01 19:12 ` [PATCH V2 3/3] acpi, apei: use EFI memmap to map GHES memory Jonathan (Zhixiong) Zhang
2015-06-05 9:57 ` Matt Fleming
2015-06-05 10:25 ` Borislav Petkov
2015-06-05 17:05 ` Zhang, Jonathan Zhixiong
2015-06-05 17:12 ` Borislav Petkov
2015-06-05 21:43 ` Zhang, Jonathan Zhixiong
2015-06-05 16:43 ` Zhang, Jonathan Zhixiong
2015-06-05 16:50 ` Borislav Petkov
2015-06-05 17:06 ` Zhang, Jonathan Zhixiong [this message]
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=5571D731.4000809@codeaurora.org \
--to=zjzhang@codeaurora.org \
--cc=al.stone@linaro.org \
--cc=bp@alien8.de \
--cc=fu.wei@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@gmail.com \
--cc=vgandhi@codeaurora.org \
--cc=ying.huang@intel.com \
/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).