From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH] linux-bb.org: Remove unneeded patches
Date: Mon, 23 Oct 2023 13:02:24 -0400 [thread overview]
Message-ID: <20231023170224.GT2408@denix.org> (raw)
In-Reply-To: <20231023155107.12518-1-reatmon@ti.com>
On Mon, Oct 23, 2023 at 10:51:07AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> With the move to the 6.1 kernel, we no longer need any of the 5.10 based
> patches.
Yeah, I was running master builds over the weekend and noticed master had
those extra gcc13 patches that kirkstone didn't have... Thanks for the fix.
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb b/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
> index a416adcb..4b921919 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
> @@ -31,11 +31,6 @@ BRANCH:aarch64 = "v6.1.46-ti-arm64-r9"
>
> SRC_URI = "git://github.com/beagleboard/linux.git;protocol=https;branch=${BRANCH} \
> file://defconfig \
> - file://init_disassemble_info-signature-changes-causes-compile-failures.patch \
> - file://0001-gcc-plugins-Fix-build-for-upcoming-GCC-release.patch \
> - file://0001-ata-ahci-fix-enum-constants-for-gcc-13.patch \
> - file://0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch \
> - file://0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch \
> "
>
> FILES:${KERNEL_PACKAGE_NAME}-devicetree += " \
> --
> 2.17.1
prev parent reply other threads:[~2023-10-23 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 15:51 [meta-ti][master][PATCH] linux-bb.org: Remove unneeded patches Ryan Eatmon
2023-10-23 17:02 ` Denys Dmytriyenko [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=20231023170224.GT2408@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).