From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Colin Finck" <c.finck@enlyze.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] networkd-dispatcher: Update to 2.2.1 to fix CVE-2022-29799 and CVE-2022-29800
Date: Wed, 4 May 2022 09:44:33 +0200 [thread overview]
Message-ID: <20220504094433.26b5b4e0@melee> (raw)
In-Reply-To: <20220503130957.282-1-c.finck@enlyze.com>
Hi Colin,
Il giorno Tue, 3 May 2022 15:09:57 +0200
"Colin Finck" <c.finck@enlyze.com> ha scritto:
> Signed-off-by: Colin Finck <c.finck@enlyze.com>
> ---
> ...{networkd-dispatcher_2.1.bb => networkd-dispatcher_2.2.1.bb} | 2
> +- 1 file changed, 1 insertion(+), 1 deletion(-)
> rename
> meta-networking/recipes-daemons/networkd-dispatcher/{networkd-dispatcher_2.1.bb
> => networkd-dispatcher_2.2.1.bb} (95%)
Thank you for your patch, but meta-networking is not part of oe-core.
It's part of meta-oe, so you should send it to the appropriate mailing
list.
Best regards.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-05-04 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 13:09 [PATCH] networkd-dispatcher: Update to 2.2.1 to fix CVE-2022-29799 and CVE-2022-29800 Colin Finck
2022-05-04 7:44 ` Luca Ceresoli [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=20220504094433.26b5b4e0@melee \
--to=luca.ceresoli@bootlin.com \
--cc=c.finck@enlyze.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox