From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Cc: nd@arm.com
Subject: [PATCH 1/9] lzo: Add further info to a patch
Date: Tue, 24 May 2022 16:23:53 +0100 [thread overview]
Message-ID: <20220524152401.1663317-1-ross.burton@arm.com> (raw)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Add some further info to the patch based on upsream changes. Given the last release
in 2017 and glaring issues on at least armv5, it does raise the question on whether
we should drop this. There are probably better compression tools now.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../lzo/0001-Use-memcpy-instead-of-reinventing-it.patch | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch b/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch
index db3a70e8031..4e6ca4132b5 100644
--- a/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch
+++ b/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch
@@ -10,6 +10,13 @@ Change suggested by Julian Taylor.
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757037
+RP: Patch is still in debian as of 20220524 in a revised form:
+https://sources.debian.org/patches/lzo2/2.10-2/
+https://sources.debian.org/patches/lzo2/2.10-2/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch/
+
+We likely need this in OE to prevent against unaligned accesses
+on systems such as armv5.
+
Upstream-Status: Pending
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
--
2.25.1
next reply other threads:[~2022-05-24 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 15:23 Ross Burton [this message]
2022-05-24 15:23 ` [PATCH 2/9] btrfs-tools: add a PACKAGECONFIG for lzo Ross Burton
2022-05-24 15:23 ` [PATCH 3/9] mtd-utils: disable LZO by default Ross Burton
2022-05-25 9:33 ` [OE-core] " richard.purdie
2022-05-25 10:34 ` Ross Burton
2022-05-25 11:38 ` richard.purdie
2022-05-24 15:23 ` [PATCH 4/9] squashfs-tools: " Ross Burton
2022-05-24 15:23 ` [PATCH 5/9] libarchive: " Ross Burton
2022-05-24 15:23 ` [PATCH 6/9] lzop: remove recipe from oe-core Ross Burton
2022-05-24 15:23 ` [PATCH 7/9] oeqa/selftest/imagefeatures: don't exercise lzo compression Ross Burton
2022-05-24 15:24 ` [PATCH 8/9] packagegroup-self-hosted: remove lzo Ross Burton
2022-05-24 15:24 ` [PATCH 9/9] lzo: remove recipe from oe-core Ross Burton
2022-05-25 8:03 ` [OE-core] " Luca Ceresoli
2022-05-25 11:26 ` Ross Burton
2022-05-25 12:59 ` Bruce Ashfield
2022-05-25 13:45 ` Ross Burton
2022-05-25 13:55 ` Bruce Ashfield
2022-05-25 8:00 ` [OE-core] [PATCH 1/9] lzo: Add further info to a patch Luca Ceresoli
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=20220524152401.1663317-1-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=nd@arm.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.