From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Diego Sueiro <diego.sueiro@arm.com>
Cc: meta-virtualization@lists.yoctoproject.org, nd <nd@arm.com>
Subject: Re: [meta-virtualization][hardknott][PATCH] k3s: Bump to v1.20.11+k3s2
Date: Tue, 12 Oct 2021 14:02:01 -0400 [thread overview]
Message-ID: <CADkTA4MtVO9=6=mi2W8YDAVSPV9KwTx+H3BLpUgi++zqqnWRVg@mail.gmail.com> (raw)
In-Reply-To: <9b56a9db183fd6725e570d16365e627905cdbbdf.1634060903.git.diego.sueiro@arm.com>
We can't bump hardknott ahead of master, but as it turns out, I
already have pending k*s updates for master, so I can cherry pick them
to the stable branches after I'm finished testing.
Bruce
On Tue, Oct 12, 2021 at 1:52 PM Diego Sueiro <diego.sueiro@arm.com> wrote:
>
> Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
> ---
> recipes-containers/k3s/k3s_git.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-containers/k3s/k3s_git.bb b/recipes-containers/k3s/k3s_git.bb
> index 2811fb8..f51d9d4 100644
> --- a/recipes-containers/k3s/k3s_git.bb
> +++ b/recipes-containers/k3s/k3s_git.bb
> @@ -13,9 +13,9 @@ SRC_URI = "git://github.com/rancher/k3s.git;branch=release-1.20;name=k3s \
> file://0001-Finding-host-local-in-usr-libexec.patch;patchdir=src/import \
> "
> SRC_URI[k3s.md5sum] = "363d3a08dc0b72ba6e6577964f6e94a5"
> -SRCREV_k3s = "bc400f5396a3dd05584c5f45768a5ea6c43971d1"
> +SRCREV_k3s = "9cb5fb5716bdfb13e755206aff5688961f5bafb3"
>
> -PV = "v1.20.4+k3s1"
> +PV = "v1.20.11+k3s2"
>
> CNI_NETWORKING_FILES ?= "${WORKDIR}/cni-containerd-net.conf"
>
> --
> 2.17.1
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2021-10-12 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 17:52 [meta-virtualization][hardknott][PATCH] k3s: Bump to v1.20.11+k3s2 Diego Sueiro
2021-10-12 18:02 ` Bruce Ashfield [this message]
2021-10-12 18:07 ` Bruce Ashfield
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='CADkTA4MtVO9=6=mi2W8YDAVSPV9KwTx+H3BLpUgi++zqqnWRVg@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=diego.sueiro@arm.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).