From: Kevin Hilman <khilman@baylibre.com>
To: Alexey Brodkin <alexey.brodkin@synopsys.com>,
linux-snps-arc@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Vineet Gupta <vineet.gupta1@synopsys.com>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ARC: change defconfig defaults to ARCv2
Date: Fri, 30 Nov 2018 13:30:59 -0800 [thread overview]
Message-ID: <7hva4e45ik.fsf@baylibre.com> (raw)
In-Reply-To: <20181130125156.34460-1-abrodkin@synopsys.com>
Alexey Brodkin <alexey.brodkin@synopsys.com> writes:
> From: Kevin Hilman <khilman@baylibre.com>
>
> Change the default defconfig (used with 'make defconfig') to the ARCv2
> nsim_hs_defconfig, and also switch the default Kconfig ISA selection to
> ARCv2.
>
> This allows several default defconfigs (e.g. make defconfig, make
> allnoconfig, make tinyconfig) to all work with ARCv2 by default.
>
> Note since we change default architecture from ARCompact to ARCv2
> it's required to explicitly mention architecture type in ARCompact
> defconfigs otherwise ARCv2 will be implied and binaries will be
> generated for ARCv2.
>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: <stable@vger.kernel.org> # 4.4.x
Tested-by: Kevin Hilman <khilman@baylibre.com>
Nice, thanks for cleaning this up. I tested it again for the kernelCI
use cases, and it's still working.
Thanks,
Kevin
next prev parent reply other threads:[~2018-12-01 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 12:51 [PATCH v2] ARC: change defconfig defaults to ARCv2 Alexey Brodkin
2018-11-30 18:55 ` Vineet Gupta
2018-11-30 21:30 ` Kevin Hilman [this message]
[not found] ` <20181202064929.9B32D20851@mail.kernel.org>
2018-12-03 10:24 ` Alexey Brodkin
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=7hva4e45ik.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=alexey.brodkin@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=vineet.gupta1@synopsys.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).