public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "Martin.Jansa@gmail.com" <Martin.Jansa@gmail.com>,
	"akuster808@gmail.com" <akuster808@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [zeus 0/7] Merge request
Date: Wed, 29 Apr 2020 04:35:28 +0000	[thread overview]
Message-ID: <989e478d2c7a6a7be60eb805e664bd5dcf678424.camel@intel.com> (raw)
In-Reply-To: <CA+chaQfuCTZYou7qcUagwBpMHS51KW2VT6yt2L1ugySLuQ7a_w@mail.gmail.com>

On Tue, 2020-04-28 at 20:07 +0200, Martin Jansa wrote:
> Hi,
> 
> can you please include:
> https://lists.openembedded.org/g/openembedded-core/topic/zeus_patch_qemu_replace/73197049?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,80,73197049
> 
> or did I misunderstood your last reply in that thread?

I have included it along with some other patches and it'd be in the
next merge request:

https://git.openembedded.org/openembedded-core-contrib/log/?h=anujm/zeus

Thanks,

Anuj

> 
> On Tue, Apr 28, 2020 at 4:16 AM akuster <akuster808@gmail.com> wrote:
> > Please consider these changes for zeus
> > The following changes since commit
> > 5ac98c776f9b77804a0ee812f47f3ecf593e432f:
> > 
> >   kernelsrc.bbclass: Fix externalsrc support (2020-04-06 15:17:05
> > +0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.openembedded.org/openembedded-core-contrib stable/zeus-
> > next
> >   
> > http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/zeus-next
> > 
> > Adrian Bunk (1):
> >   openssl: Upgrade 1.1.1d -> 1.1.1e
> > 
> > Alexander Kanavin (1):
> >   openssl: update to 1.1.1f
> > 
> > Denys Dmytriyenko (1):
> >   openssl: recommend cryptodev-module for corresponding
> > PACKAGECONFIG
> > 
> > Lee Chee Yang (2):
> >   cve-check: CPE version '-' as all version
> >   wic: align layer plugin path
> > 
> > Ovidiu Panait (1):
> >   inetutils: Use alternatives to avoid manpage conflict
> > 
> > Richard Purdie (1):
> >   pseudo: Ensure we use our own libsqlite
> > 
> >  meta/classes/cve-check.bbclass                |   2 +-
> >  .../inetutils/inetutils_1.9.4.bb              |   6 +-
> >  .../openssl/openssl/CVE-2019-1551.patch       | 758 --------------
> > ----
> >  .../{openssl_1.1.1d.bb => openssl_1.1.1f.bb}  |   6 +-
> >  .../recipes-core/meta/cve-update-db-native.bb |   2 +-
> >  meta/recipes-devtools/pseudo/pseudo.inc       |   2 +
> >  scripts/lib/wic/help.py                       |   3 +-
> >  scripts/lib/wic/pluginbase.py                 |  11 +-
> >  8 files changed, 19 insertions(+), 771 deletions(-)
> >  delete mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-
> > 2019-1551.patch
> >  rename meta/recipes-connectivity/openssl/{openssl_1.1.1d.bb =>
> > openssl_1.1.1f.bb} (97%)
> > 
> > 

      reply	other threads:[~2020-04-29  4:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  2:15 [zeus 0/7] Merge request akuster
2020-04-28  2:15 ` [zeus 1/7] cve-check: CPE version '-' as all version akuster
2020-04-28  2:15 ` [zeus 2/7] pseudo: Ensure we use our own libsqlite akuster
2020-04-28  2:15 ` [zeus 3/7] wic: align layer plugin path akuster
2020-04-28  2:15 ` [zeus 4/7] inetutils: Use alternatives to avoid manpage conflict akuster
2020-04-28  2:15 ` [zeus 5/7] openssl: recommend cryptodev-module for corresponding PACKAGECONFIG akuster
2020-04-28  2:15 ` [zeus 6/7] openssl: Upgrade 1.1.1d -> 1.1.1e akuster
2020-04-28  2:15 ` [zeus 7/7] openssl: update to 1.1.1f akuster
2020-04-28 16:13 ` [OE-core] [zeus 0/7] Merge request Jan Luebbe
2020-04-28 17:09   ` akuster
2020-05-04 13:42     ` Jan Luebbe
2020-05-04 14:18       ` Steve Sakoman
2020-04-28 18:07 ` Martin Jansa
2020-04-29  4:35   ` Anuj Mittal [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=989e478d2c7a6a7be60eb805e664bd5dcf678424.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=Martin.Jansa@gmail.com \
    --cc=akuster808@gmail.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