linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Tony Lindgren <tony@atomide.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: kernel: compiling issue, need delete read_current_timer().
Date: Thu, 13 Jun 2013 09:13:45 +0800	[thread overview]
Message-ID: <51B91CC9.3050707@asianux.com> (raw)
In-Reply-To: <51B594F2.9030000@arm.com>

On 06/10/2013 04:57 PM, Marc Zyngier wrote:
> Sorry for the delay replying. This looks good to me.
> 
> FWIW:
> Acked-by: Marc Zyngier <marc.zyngier@arm.com>

Thanks, also sorry for my delay replying.

-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-06-13  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5199C725.8050102@asianux.com>
     [not found] ` <168084c28e8ba5124c05553e97463172@localhost>
     [not found]   ` <20130520095606.GH31359@mudshark.cambridge.arm.com>
     [not found]     ` <519AF2DC.2040200@asianux.com>
     [not found]       ` <20130521085325.GB10453@mudshark.cambridge.arm.com>
     [not found]         ` <519B425D.4030806@asianux.com>
2013-05-27 10:02           ` [PATCH v2] arm64: kernel: compiling issue, need delete read_current_timer() Chen Gang
2013-06-08  4:37             ` Chen Gang
2013-06-10  8:57               ` Will Deacon
2013-06-13  1:12                 ` Chen Gang
2013-06-10  8:57               ` Marc Zyngier
2013-06-13  1:13                 ` Chen Gang [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=51B91CC9.3050707@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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).