From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
Mark Hatle <mark.hatle@kernel.crashing.org>,
Marta Rybczynska <rybczynska@gmail.com>,
Steve Sakoman <steve@sakoman.com>,
Ross Burton <ross.burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] cve-update-nvd2-native: add workaround for json5 style list
Date: Thu, 10 Apr 2025 11:51:26 +0100 [thread overview]
Message-ID: <94d6ad67f316255e5433cc35cdd65c99ae9d58ee.camel@linuxfoundation.org> (raw)
In-Reply-To: <AS1PR10MB56975DE1234794F5DCDC4FC5FDB72@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Thu, 2025-04-10 at 10:43 +0000, Marko, Peter wrote:
> The patch was just merged to master.
> I'll send patches for LTS (kirkstone/scarthgap) in the evening, but
> maybe Steve can just pick them from master quicker as they should
> apply cleanly.
>
> As I mention in the patch itself, it's hard to design a stable
> solution if we don't know the reasons for broken jsons.
> For now I'm plugging the holes as they arise (monitored by nightly
> pipeline).
> I'd give it a month or two to see stability of FKIE/NVD1 feeds and
> then we should revisit backports of these to LTS.
FWIW this seems like the best plan to me. Things are very much in flux
and seem likely to change. I'll merge it to walnascar in the meantime.
Cheers,
Richard
prev parent reply other threads:[~2025-04-10 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 9:35 [OE-core][PATCH] cve-update-nvd2-native: add workaround for json5 style list Peter Marko
2025-04-07 9:45 ` Marko, Peter
2025-04-09 16:32 ` Mark Hatle
2025-04-10 10:43 ` Marko, Peter
2025-04-10 10:51 ` Richard Purdie [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=94d6ad67f316255e5433cc35cdd65c99ae9d58ee.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Peter.Marko@siemens.com \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=rybczynska@gmail.com \
--cc=steve@sakoman.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