All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [PATCH] ffa-debugfs-mod: Do not build for TI SOCs
Date: Tue, 3 May 2022 09:06:52 -0400	[thread overview]
Message-ID: <YnEo7I/HCeTzmtBY@kudzu.us> (raw)
In-Reply-To: <20220501184731.3730441-1-raj.khem@gmail.com>

On Sun, May 01, 2022 at 11:47:31AM -0700, Khem Raj wrote:
> The module can not be compiled without patching kernel 5.10
> This helps meta-ti to live in multi-BSP envs
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  meta-arm/recipes-kernel/ffa-debugfs/ffa-debugfs-mod_2.1.0.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta-arm/recipes-kernel/ffa-debugfs/ffa-debugfs-mod_2.1.0.bb b/meta-arm/recipes-kernel/ffa-debugfs/ffa-debugfs-mod_2.1.0.bb
> index 4051c34..a4dd38c 100644
> --- a/meta-arm/recipes-kernel/ffa-debugfs/ffa-debugfs-mod_2.1.0.bb
> +++ b/meta-arm/recipes-kernel/ffa-debugfs/ffa-debugfs-mod_2.1.0.bb
> @@ -27,6 +27,7 @@ do_install:append() {
>  }
>  
>  COMPATIBLE_HOST = "(arm|aarch64).*-linux"
> +COMPATIBLE_HOST:ti-soc = "null"

Shouldn't this live in meta-ti?

>  
>  # Kernel modules currently RDEPEND on the kernel, which is troublesome when you want to put a
>  # kernel module into a initramfs without pulling the kernel into the initramfs, which would be
> -- 
> 2.36.0
> 
> 


  reply	other threads:[~2022-05-03 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 18:47 [PATCH] ffa-debugfs-mod: Do not build for TI SOCs Khem Raj
2022-05-03 13:06 ` Jon Mason [this message]
2022-05-03 14:48   ` Khem Raj
2022-05-03 15:21     ` [meta-arm] " Denys Dmytriyenko
2022-05-03 15:54       ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2022-05-03 15:09 Khem Raj

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=YnEo7I/HCeTzmtBY@kudzu.us \
    --to=jdmason@kudzu.us \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=raj.khem@gmail.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.