From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] linux: fix CIP RT kernel on microblaze
Date: Sun, 26 Feb 2023 18:43:32 +0100 [thread overview]
Message-ID: <20230226184332.39c3a9b2@windsurf> (raw)
In-Reply-To: <20230225170229.358936-1-fontaine.fabrice@gmail.com>
On Sat, 25 Feb 2023 18:02:29 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 7645b5f507..f3fdc40328 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -33,6 +33,7 @@ LINUX_SITE_METHOD = svn
> else ifeq ($(BR2_LINUX_KERNEL_LATEST_CIP_VERSION)$(BR2_LINUX_KERNEL_LATEST_CIP_RT_VERSION),y)
> LINUX_SOURCE = linux-cip-$(LINUX_VERSION).tar.gz
> LINUX_SITE = https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/snapshot
> +LINUX_PATCHES += linux/cip-rt/0001-arch-microblaze-mm-init.c-fix-build.patch
Why not put the patch in linux/5.10.162-cip24-rt10/ directly? This way
it would automatically be applied, with the need to tweak LINUX_PATCHES.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-02-26 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 17:02 [Buildroot] [PATCH 1/1] linux: fix CIP RT kernel on microblaze Fabrice Fontaine
2023-02-26 17:43 ` Thomas Petazzoni via buildroot [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=20230226184332.39c3a9b2@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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