From: Nylon Chen <nylon7@andestech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/nds32: force syntax colouring to kconfig.
Date: Thu, 6 Jun 2019 14:40:55 +0800 [thread overview]
Message-ID: <20190606064055.GA20024@app09> (raw)
In-Reply-To: <20190603191951.22360-1-yann.morin.1998@free.fr>
On Tue, Jun 04, 2019 at 03:19:51AM +0800, Yann E. MORIN wrote:
> It is too sad when an editor picks up the wrong syntax...
>
> Like was done in e837837791 for all the other archs, force
> syntax to kconfig for nds32 too.
>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Nylon Chen <nylon7@andestech.com>
> ---
> arch/Config.in.nds32 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/Config.in.nds32 b/arch/Config.in.nds32
> index f268883662..322ff49f2e 100644
> --- a/arch/Config.in.nds32
> +++ b/arch/Config.in.nds32
> @@ -9,3 +9,6 @@ config BR2_ENDIAN
>
> config BR2_READELF_ARCH_NAME
> default "Andes Technology compact code size embedded RISC processor family"
> +
> +# vim: ft=kconfig
> +# -*- mode:kconfig; -*-
> --
> 2.20.1
>
Reviewed-by:Nylon Chen <nylon7@andestech.com>
next prev parent reply other threads:[~2019-06-06 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 19:19 [Buildroot] [PATCH] arch/nds32: force syntax colouring to kconfig Yann E. MORIN
2019-06-06 6:40 ` Nylon Chen [this message]
2019-06-20 19:27 ` 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=20190606064055.GA20024@app09 \
--to=nylon7@andestech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox