[1/9] lzo: Add further info to a patch

Message ID	20220524152401.1663317-1-ross.burton@arm.com
State	New
Headers	show Return-Path: <ross.burton@arm.com> ip: 217.140.110.172, mailfrom: ross.burton@arm.com) 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 Message-Id: <20220524152401.1663317-1-ross.burton@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable
Series	[1/9] lzo: Add further info to a patch \| expand [1/9] lzo: Add further info to a patch [2/9] btrfs-tools: add a PACKAGECONFIG for lzo [3/9] mtd-utils: disable LZO by default [4/9] squashfs-tools: disable LZO by default [5/9] libarchive: disable LZO by default [6/9] lzop: remove recipe from oe-core [7/9] oeqa/selftest/imagefeatures: don't exercise lzo compression [8/9] packagegroup-self-hosted: remove lzo [9/9] lzo: remove recipe from oe-core

Message ID

20220524152401.1663317-1-ross.burton@arm.com

State

New

Headers

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
Message-Id: <20220524152401.1663317-1-ross.burton@arm.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Series

[1/9] lzo: Add further info to a patch | expand

Commit Message

Ross Burton May 24, 2022, 3:23 p.m. UTC

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(+)

Comments

Luca Ceresoli May 25, 2022, 8 a.m. UTC | #1

Hi Richard,

Il giorno Tue, 24 May 2022 16:23:53 +0100
"Ross Burton" <ross.burton@arm.com> ha scritto:

> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> 
> Add some further info to the patch based on upsream changes. Given

s/upsream/upstream/

Fixing it in my master-next branch.

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>
 ---