From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3 v2] arm64: defconfig updates
Date: Wed, 27 Apr 2016 10:13:48 +0800 [thread overview]
Message-ID: <20160427021348.GF30692@tiger> (raw)
In-Reply-To: <HE1PR04MB1641EB5615245CC5A5BE041F8D630@HE1PR04MB1641.eurprd04.prod.outlook.com>
On Tue, Apr 26, 2016 at 01:52:06PM +0000, Stuart Yoder wrote:
>
>
> > -----Original Message-----
> > From: Shawn Guo [mailto:shawnguo at kernel.org]
> > Sent: Tuesday, April 26, 2016 5:16 AM
> > To: Stuart Yoder <stuart.yoder@nxp.com>
> > Cc: linux-arm-kernel at lists.infradead.org; catalin.marinas at arm.com; will.deacon at arm.com;
> > kernel at pengutronix.de; Yang-Leo Li <leoyang.li@nxp.com>; Scott Wood <scott.wood@nxp.com>;
> > marc.zyngier at arm.com; mark.rutland at arm.com
> > Subject: Re: [PATCH 0/3 v2] arm64: defconfig updates
> >
> > On Wed, Apr 20, 2016 at 10:57:16AM -0500, Stuart Yoder wrote:
> > > Stuart Yoder (3):
> > > arm64: defconfig: cleanup the defconfig
> > > arm64: defconfig: enable 48-bit virtual addresses
> >
> > Applied these two.
> >
> > > arm64: defconfig: enable freescale/nxp config options
> >
> > But this one doesn't apply to v4.6-rc1.
>
> Yes. There is a patch from Will that went into rc2 that was a major
> defconfig update:
> 431597b arm64: defconfig: updates for 4.6
>
> ...so basing my patch on rc1 would have caused it not to apply to
> later kernels.
Okay, I rebased my defconfig64 branch onto v4.6-rc2 and applied all 3
patches.
Shawn
prev parent reply other threads:[~2016-04-27 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 15:57 [PATCH 0/3 v2] arm64: defconfig updates Stuart Yoder
2016-04-26 10:15 ` Shawn Guo
2016-04-26 13:52 ` Stuart Yoder
2016-04-27 2:13 ` Shawn Guo [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=20160427021348.GF30692@tiger \
--to=shawnguo@kernel.org \
--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).