From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RESEND] arm/arm64: Move barrier instructions into separate header
Date: Thu, 12 May 2016 12:33:16 +0100 [thread overview]
Message-ID: <1463052796.1876.9.camel@hellion.org.uk> (raw)
In-Reply-To: <1463051681-19428-1-git-send-email-andre.przywara@arm.com>
On Thu, 2016-05-12 at 12:14 +0100, Andre Przywara wrote:
> ---
> Hi Hans, Ian,
>
> can I get an ACK on this please?
I'm afraid that given:
[...]
> ?arch/arm/include/asm/armv7.h???????| 21 +-----------------
> ?arch/arm/include/asm/barriers.h????| 44 ++++++++++++++++++++++++++++++++++++++
> ?arch/arm/mach-sunxi/dram_helpers.c |??2 +-
It's not really our Ack you need, but the overall arm maintainer's
(Albert) ack. (AFAIK there is no separate armv8 maintainer.)
FIW for the sunxi hunk:
Acked-by: Ian Campbell <ijc@hellion.org.uk>
Although it is so trivial as to be hardly worth it.
Ian.
next prev parent reply other threads:[~2016-05-12 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 11:14 [U-Boot] [PATCH RESEND] arm/arm64: Move barrier instructions into separate header Andre Przywara
2016-05-12 11:33 ` Ian Campbell [this message]
2016-05-12 15:13 ` Tom Rini
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=1463052796.1876.9.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=u-boot@lists.denx.de \
/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