From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/snps_archs38_zebu: rename zebu to haps
Date: Mon, 24 Apr 2017 13:30:01 +0000 [thread overview]
Message-ID: <1493040601.2643.10.camel@synopsys.com> (raw)
In-Reply-To: <1492532385-24563-1-git-send-email-vzakhar@synopsys.com>
Hi Thomas, Peter,
On Tue, 2017-04-18 at 19:19 +0300, Vlad Zakharov wrote:
> As in upstream Linux zebu_hs_smp_defconfig was renamed to
> haps_hs_smp_defconfig we update Linux kernel defconfig name
> respectively.
>
> Also it fixes build failure, pointed us by Arnout:
> https://gitlab.com/buildroot.org/buildroot/builds/14419271
>
> Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
> ---
> ?configs/{snps_archs38_zebu_defconfig => snps_archs38_haps_defconfig} | 2 +-
> ?1 file changed, 1 insertion(+), 1 deletion(-)
> ?rename configs/{snps_archs38_zebu_defconfig => snps_archs38_haps_defconfig} (91%)
>
> diff --git a/configs/snps_archs38_zebu_defconfig b/configs/snps_archs38_haps_defconfig
> similarity index 91%
> rename from configs/snps_archs38_zebu_defconfig
> rename to configs/snps_archs38_haps_defconfig
> index 98beb2b..4f03560 100644
> --- a/configs/snps_archs38_zebu_defconfig
> +++ b/configs/snps_archs38_haps_defconfig
> @@ -14,5 +14,5 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_10=y
> ?BR2_LINUX_KERNEL=y
> ?BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> ?BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.10.9"
> -BR2_LINUX_KERNEL_DEFCONFIG="zebu_hs_smp"
> +BR2_LINUX_KERNEL_DEFCONFIG="haps_hs_smp"
> ?BR2_LINUX_KERNEL_VMLINUX=y
Please treat this message how a polite remainder to review this patch.
Thanks.
--
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>
next prev parent reply other threads:[~2017-04-24 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 16:19 [Buildroot] [PATCH] configs/snps_archs38_zebu: rename zebu to haps Vlad Zakharov
2017-04-18 17:22 ` Arnout Vandecappelle
2017-04-24 13:30 ` Vlad Zakharov [this message]
2017-05-07 12:01 ` Thomas Petazzoni
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=1493040601.2643.10.camel@synopsys.com \
--to=vladislav.zakharov@synopsys.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.