All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: akuster <akuster808@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-security][PATCH] libseccomp: update to 2.4.3
Date: Sat, 7 Mar 2020 17:18:07 -0500	[thread overview]
Message-ID: <20200307221807.GG1578@denix.org> (raw)
In-Reply-To: <20200307203849.3117-1-akuster808@gmail.com>

On Sat, Mar 07, 2020 at 08:38:49PM +0000, akuster wrote:
> dropped patch now included in update

Do you want to remove the patch?


> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
>  .../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb}    | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>  rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)
> 
> diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
> similarity index 90%
> rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
> rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
> index 07db82a..9ca41e6 100644
> --- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
> +++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
> @@ -4,10 +4,9 @@ SECTION = "security"
>  LICENSE = "LGPL-2.1"
>  LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"
>  
> -SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
> +SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"
>  
>  SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
> -           file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
>             file://run-ptest \
>  "
>  
> -- 
> 2.17.1
> 

> 


  reply	other threads:[~2020-03-07 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 20:38 [meta-security][PATCH] libseccomp: update to 2.4.3 akuster
2020-03-07 22:18 ` Denys Dmytriyenko [this message]
2020-03-08  3:53   ` [yocto] " akuster

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=20200307221807.GG1578@denix.org \
    --to=denis@denix.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.