From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] coresight: Adding coresight support for arm64 architecture
Date: Thu, 12 Feb 2015 09:49:11 +0000 [thread overview]
Message-ID: <20150212094911.GA1028@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <CANLsYky9sGK=vpEM5kMD8HZJ_a+hyU58sV=u=KHe9+oKGhGCqA@mail.gmail.com>
On Wed, Feb 11, 2015 at 07:54:04PM -0700, Mathieu Poirier wrote:
> On 11 February 2015 at 04:36, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poirier at 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>
>
> I intended to merge both patches via my tree and as such ensuring the
> Kconfig changes and compilation warnings fix go in at the same time.
> Is this fine with you?
It was more about bisectability. If reordering is problematic (already
published branch etc.), leave them as they are.
--
Catalin
next prev parent reply other threads:[~2015-02-12 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 4:31 [PATCH v3 1/2] coresight: Adding coresight support for arm64 architecture mathieu.poirier at linaro.org
2015-02-11 4:31 ` [PATCH v3 2/2] coresight: fixing compilation warnings picked up by 64bit compiler mathieu.poirier at linaro.org
2015-02-11 11:36 ` [PATCH v3 1/2] coresight: Adding coresight support for arm64 architecture Catalin Marinas
2015-02-12 2:54 ` Mathieu Poirier
2015-02-12 9:49 ` Catalin Marinas [this message]
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=20150212094911.GA1028@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).