From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Kris Bahnsen <kris@embeddedTS.com>
Cc: Julien Grossholtz <julien.grossholtz@openest.io>,
Mark Featherston <mark@embeddedTS.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/ts7680: bump Linux version to 4.9.311
Date: Sun, 17 Jul 2022 09:30:40 +0200 [thread overview]
Message-ID: <20220717073040.GZ2543@scaer> (raw)
In-Reply-To: <20220714220805.29298-1-kris@embeddedTS.com>
Kris, All,
On 2022-07-14 15:08 -0700, Kris Bahnsen via buildroot spake thusly:
> Signed-off-by: Kris Bahnsen <kris@embeddedTS.com>
Applied to master, thanks.
> ---
>
> I'm also happy to add myself or be added to DEVELOPERS for this and other
> embeddedTS devices. I'm just unsure of procedure for doing so.
Just edit the DEVELOPERS file, add your name in alphabetical order with
an 'N' field, and add the files and directories/ you would like to
monitor, still in alphabetical order, as 'F' fields. Noe that wildcards
are not supported. For configs/ts7680, that would be something like
(fields and values are separated by a TAB » ):
N:»Kris Bahnsen <kris@embeddedTS.com>
F:»configs/ts7680_defconfig
You can test that it works:
$ ./utils/get-developers -f configs/ts7680_defconfig
Julien Grossholtz <julien.grossholtz@openest.io>
Kris Bahnsen <kris@embeddedTS.com>
Thanks!
Regards,
Yann E. MORIN.
> configs/ts7680_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/ts7680_defconfig b/configs/ts7680_defconfig
> index e4f5c1aabd..9e058b1d78 100644
> --- a/configs/ts7680_defconfig
> +++ b/configs/ts7680_defconfig
> @@ -4,7 +4,7 @@ BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/technologic/ts7680/genimage.cfg"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,embeddedTS,linux-4.9.y,d03d426e6abd95a973bc669315206295713c17e8)/linux-d03d426e6abd95a973bc669315206295713c17e8.tar.gz"
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,embeddedTS,linux-4.9.y,v4.9.311-ts)/linux-v4.9.311-ts.tar.gz"
> BR2_LINUX_KERNEL_DEFCONFIG="ts_imx28"
> BR2_LINUX_KERNEL_UIMAGE=y
> BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x40008000"
> --
> 2.11.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-17 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 22:08 [Buildroot] [PATCH 1/1] configs/ts7680: bump Linux version to 4.9.311 Kris Bahnsen via buildroot
2022-07-17 7:30 ` Yann E. MORIN [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=20220717073040.GZ2543@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=julien.grossholtz@openest.io \
--cc=kris@embeddedTS.com \
--cc=mark@embeddedTS.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 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.