All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] libxml2: fix unsafe memory access
Date: Wed, 28 Oct 2015 12:55:21 +0200	[thread overview]
Message-ID: <5630A999.1030605@linux.intel.com> (raw)
In-Reply-To: <56309F82.203@windriver.com>

On 10/28/2015 12:12 PM, Kang Kai wrote:
>> This may be a nitpick but I don't think DV has taken this patch in the
>> six months it's been available so it's not a backport.
>
> I suppose Backport is the best choice in upstream status [ Pending
> Submitted Accepted Backport Denied Inappropriate ]. Though it is not
> from official upstream, it is from somewhere else as listed in the patch.

'Submitted [where]' is the right choice here, I think.


Alex


  reply	other threads:[~2015-10-28 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  5:22 [PATCH 0/1] Fix libxml2 unsafe memory access kai.kang
2015-10-28  5:22 ` [PATCH 1/1] libxml2: fix " kai.kang
2015-10-28  9:41   ` Jussi Kukkonen
2015-10-28 10:12     ` Kang Kai
2015-10-28 10:55       ` Alexander Kanavin [this message]
2015-10-28 11:15         ` Burton, Ross
2015-10-29  1:43           ` Kang Kai

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=5630A999.1030605@linux.intel.com \
    --to=alexander.kanavin@linux.intel.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 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.