From: Denys Dmytriyenko <denis@denix.org>
To: Bryan Brattlof <bb@ti.com>
Cc: Ryan Eatmon <reatmon@ti.com>, Andrew Davis <afd@ti.com>,
Meta-TI <meta-ti@lists.yoctoproject.org>, Res Sapp <rs@ti.com>
Subject: Re: [meta-ti kirkstone/master PATCH] ti-kernel: Apply RT config fragments to RT kernel defconfig
Date: Thu, 1 Jun 2023 15:25:50 -0400 [thread overview]
Message-ID: <20230601192550.GL9226@denix.org> (raw)
In-Reply-To: <20230601185739.2862707-1-bb@ti.com>
On Thu, Jun 01, 2023 at 01:57:39PM -0500, Bryan Brattlof wrote:
> For the v6.1 LTS kernel, we (TI) have moved to using defconfig fragments
> to build the different kernel configurations.
FWIW, config fragments have been in use for many years...
Otherwise LGTM.
> To properly build a kernel
> with full preemption support, add the ti_arm64_rt.config to the
> linux-ti-staging-rt-6.1/k3/defconfig
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> .../recipes-kernel/linux/linux-ti-staging-rt-6.1/k3/defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.1/k3/defconfig b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.1/k3/defconfig
> index ef1d3efd50118..54dc86b407c7c 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.1/k3/defconfig
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.1/k3/defconfig
> @@ -1,2 +1,2 @@
> use-kernel-config=defconfig
> -config-fragment=kernel/configs/ti_arm64_prune.config
> +config-fragment=kernel/configs/ti_arm64_prune.config kernel/configs/ti_arm64_rt.config
>
> base-commit: 8fa9ec7dcd2e816cee18aaf7e8947b3eaee9923c
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-06-01 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 18:57 [meta-ti kirkstone/master PATCH] ti-kernel: Apply RT config fragments to RT kernel defconfig Bryan Brattlof
2023-06-01 19:25 ` Denys Dmytriyenko [this message]
2023-06-01 19:35 ` Andrew Davis
2023-06-01 20:23 ` Bryan Brattlof
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=20230601192550.GL9226@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@ti.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.