mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: mathieu.poirier@linaro.org
Cc: will.deacon@arm.com, linux@arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] coresight: Adding coresight support for arm64 architecture
Date: Wed, 11 Feb 2015 11:36:52 +0000	[thread overview]
Message-ID: <20150211113651.GC9058@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1423629085-1044-1-git-send-email-mathieu.poirier@linaro.org>

On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poirier@linaro.org wrote:
> From: Mathieu Poirier <mathieu.poirier@linaro.org>
> 
> Most CoreSight blocks are 64-bit ready.  As such move configuration
> entries from "arch/arm/Kconfig.config" to the driver's subdirectory
> and source the newly created Kconfig from architecture specific
> Kconfig.debug files.
> 
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> Change for v3:
>   - Separating Kconfig work from compilation warnings fixes.

Nitpick: merge the compilation warnings fix first so that we don't get
them once the Kconfig patch is merged for arm64.

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

  parent reply	other threads:[~2015-02-11 11:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  4:31 mathieu.poirier
2015-02-11  4:31 ` [PATCH v3 2/2] coresight: fixing compilation warnings picked up by 64bit compiler mathieu.poirier
2015-02-11 11:36 ` Catalin Marinas [this message]
2015-02-12  2:54   ` [PATCH v3 1/2] coresight: Adding coresight support for arm64 architecture Mathieu Poirier
2015-02-12  9:49     ` Catalin Marinas
2015-02-13  1:46       ` Mathieu Poirier

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=20150211113651.GC9058@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mathieu.poirier@linaro.org \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®