All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: akuster808 <akuster808@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-security][PATCH] linux-yocto: drop version from bbappends
Date: Wed, 1 Feb 2023 17:02:30 +0200	[thread overview]
Message-ID: <Y9p/BiyhHYUTaf0c@nuoska> (raw)
In-Reply-To: <87c2bde7-c0d8-a61b-f6da-5557f3347ced@gmail.com>

Hi,

On Wed, Feb 01, 2023 at 08:19:42AM -0500, akuster808 wrote:
> 
> 
> On 1/30/23 6:01 AM, Mikko Rapeli wrote:
> > These bbappends apply to multiple kernel versions so no
> > need to make them version dependent. Fixes recipe parsing when
> > using meta-security master branch on kirkstone. In our custom layer we
> > set layer compatibility for kirkstone and I understand why meta-security
> > upstream would not want to do that:
> > 
> > LAYERSERIES_COMPAT_security-layer += 'kirkstone'
> > LAYERSERIES_COMPAT_parsec-layer += 'kirkstone'
> > LAYERSERIES_COMPAT_tpm-layer += 'kirkstone'
> > 
> > While I work towards supporting also yocto master branch and newer
> > releases than kirkstone, I would appreciate if I would not have to
> > branch off layers over minor details like this.
> 
> Is this a dup of the one sent earlier?

Yes, I wasn't sure if I was on the mailing list or not and send-emailed
another one after I was correctly subscribed.

Cheers,

-Mikko

> -armin
> > 
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> >   .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
> >   .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend}    | 0
> >   2 files changed, 0 insertions(+), 0 deletions(-)
> >   rename meta-tpm/recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
> >   rename recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
> > 
> > diff --git a/meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend b/meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
> > similarity index 100%
> > rename from meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend
> > rename to meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend
> > diff --git a/recipes-kernel/linux/linux-yocto_6.%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend
> > similarity index 100%
> > rename from recipes-kernel/linux/linux-yocto_6.%.bbappend
> > rename to recipes-kernel/linux/linux-yocto_%.bbappend
> > 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#59099): https://lists.yoctoproject.org/g/yocto/message/59099
> > Mute This Topic: https://lists.yoctoproject.org/mt/96625229/3616698
> > Group Owner: yocto+owner@lists.yoctoproject.org
> > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [akuster808@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> > 
> 


      reply	other threads:[~2023-02-01 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 11:01 [meta-security][PATCH] linux-yocto: drop version from bbappends Mikko Rapeli
2023-02-01 13:19 ` [yocto] " akuster808
2023-02-01 15:02   ` Mikko Rapeli [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=Y9p/BiyhHYUTaf0c@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=akuster808@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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.