Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [zeus][PATCH 1/2] libxml2: fix CVE-2020-7595
Date: Sat, 22 Feb 2020 23:12:34 +0200	[thread overview]
Message-ID: <20200222211234.GB9628@localhost> (raw)
In-Reply-To: <3a180667-45cb-a15a-8f6b-20d49802ee71@gmail.com>

On Sat, Feb 22, 2020 at 10:50:13AM -0800, akuster808 wrote:
> On 2/21/20 1:00 PM, Adrian Bunk wrote:
> > From: Anuj Mittal <anuj.mittal@intel.com>
> >
> > Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> Is this a backport from Master?

Yes.

> please include masters commit id.

openembedded-core commit id or poky commit id?
They are always different, and I am working on top of poky.

> Since Master and Zeus are at different versions, was there anything you
> had to do to make this apply to Zeus?

There is always the trivial change to the bb file.

> I have adopted the kernel stable note of [Fixup for XXX context] so the
> folks know things had to be tweaked from the original commit.

I am already doing the same for non-trivial changes, e.g.
http://lists.openembedded.org/pipermail/openembedded-core/2020-February/293312.html

> - Armin

cu
Adrian


  reply	other threads:[~2020-02-22 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 21:00 [zeus][PATCH 1/2] libxml2: fix CVE-2020-7595 Adrian Bunk
2020-02-21 21:00 ` [zeus][PATCH 2/2] libxml2: Fix CVE-2019-20388 Adrian Bunk
2020-02-22 18:50 ` [zeus][PATCH 1/2] libxml2: fix CVE-2020-7595 akuster808
2020-02-22 21:12   ` Adrian Bunk [this message]
2020-02-23 16:33     ` akuster808

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=20200222211234.GB9628@localhost \
    --to=bunk@stusta.de \
    --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