All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/containerd: security bump to 1.6.6
Date: Sat, 6 Aug 2022 23:25:57 +0200	[thread overview]
Message-ID: <20220806232557.547ee1c8@windsurf> (raw)
In-Reply-To: <20220804054736.3221427-1-christian@paral.in>

On Wed,  3 Aug 2022 22:47:36 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:

> v1.6.2 -> v1.6.6:
> 
> The third patch release for containerd 1.6 includes various fixes and updates.
> 
> https://github.com/containerd/containerd/releases/tag/v1.6.3
> 
> The fourth patch release for containerd 1.6 includes two fixes for CNI and SELinux.
> 
> https://github.com/containerd/containerd/releases/tag/v1.6.4
> 
> The fifth patch release for containerd 1.6 includes a few fixes.
> 
> https://github.com/containerd/containerd/releases/tag/v1.6.5
> 
> The sixth patch release for containerd 1.6 includes a fix for
> CVE-2022-31030.
> 
> https://github.com/containerd/containerd/releases/tag/v1.6.6
> 
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
>  package/containerd/containerd.hash | 2 +-
>  package/containerd/containerd.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-06 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  5:47 [Buildroot] [PATCH 1/1] package/containerd: security bump to 1.6.6 Christian Stewart via buildroot
2022-08-06 21:25 ` Thomas Petazzoni via buildroot [this message]
2022-09-14 20:13   ` Peter Korsgaard

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=20220806232557.547ee1c8@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.