From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Laura Abbott <labbott@redhat.com>,
will.deacon@arm.com, linux-arch@vger.kernel.org,
keescook@chromium.org, linux-arm-kernel@lists.infradead.org,
linux@armlinux.org.uk
Subject: Re: [PATCH 0/2] arm/arm64: localise objcopy flags
Date: Tue, 19 Jul 2016 15:31:41 +0100 [thread overview]
Message-ID: <20160719143141.GF21256@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160719102925.GB27022@leverpostej>
On Tue, Jul 19, 2016 at 11:29:26AM +0100, Mark Rutland wrote:
> On Mon, Jul 18, 2016 at 04:16:34PM -0700, Laura Abbott wrote:
> > On 07/12/2016 08:28 AM, Mark Rutland wrote:
> > >Mark Rutland (2):
> > > arm64: localise Image objcopy flags
> > > arm: localise objcopy flags
> > >
> > > arch/arm/Makefile | 1 -
> > > arch/arm/boot/Makefile | 2 ++
> > > arch/arm64/Makefile | 1 -
> > > arch/arm64/boot/Makefile | 2 ++
> > > 4 files changed, 4 insertions(+), 2 deletions(-)
> > >
> >
> > Kees' lkdtm tests compile and boot successfully with this patch for
> > both arm and arm64 so you can add
> >
> > Tested-by: Laura Abbott <labbott@redhat.com>
>
> Cheers!
>
> On the assumption that Russell is ok with the arm patch, I've dropped
> that in the patch system (with tags) as 8588/1 [1].
>
> Catalin, Will, I guess I should repost the arm64 patch come v4.8-rc1?
I queued them for 4.8. Thanks.
--
Catalin
next prev parent reply other threads:[~2016-07-19 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:28 [PATCH 0/2] arm/arm64: localise objcopy flags Mark Rutland
2016-07-12 15:28 ` [PATCH 1/2] arm64: localise Image " Mark Rutland
2016-07-12 15:28 ` [PATCH 2/2] arm: localise " Mark Rutland
2016-07-12 17:03 ` [PATCH 0/2] arm/arm64: " Kees Cook
2016-07-18 23:16 ` Laura Abbott
2016-07-19 10:29 ` Mark Rutland
2016-07-19 14:31 ` Catalin Marinas [this message]
2016-07-19 14:35 ` Catalin Marinas
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=20160719143141.GF21256@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).