From: Sudeep Holla <sudeep.holla@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>, edk2-devel@lists.01.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andrew Fish <afish@apple.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH] ArmPkg: fix compilation error in ArmDmaLib
Date: Thu, 1 Dec 2016 16:46:12 +0000 [thread overview]
Message-ID: <eeab1e99-fb48-27f3-d7b9-5715772786fb@arm.com> (raw)
In-Reply-To: <20161201164502.9470-1-leif.lindholm@linaro.org>
On 01/12/16 16:45, Leif Lindholm wrote:
> Commit 0a99a65d2c8a ("fix incorrect device address of double buffer")
> retained an explicit cast on the variable "Buffer" which became
> incorrect with the other changes, leading to compilation failures
> with some toolchains. Drop the cast.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Reported-by: Sudeep Holla <sudeep.holla@arm.com>
It fixes the build for me.
Tested-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-12-01 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 16:45 [PATCH] ArmPkg: fix compilation error in ArmDmaLib Leif Lindholm
2016-12-01 16:46 ` Sudeep Holla [this message]
2016-12-01 17:00 ` Ard Biesheuvel
2016-12-01 17:07 ` Leif Lindholm
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-list 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=eeab1e99-fb48-27f3-d7b9-5715772786fb@arm.com \
--to=devel@edk2.groups.io \
/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