From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "Ross Burton" <ross.burton@arm.com>,
openembedded-core@lists.openembedded.org, nd@arm.com
Subject: Re: [OE-core] [PATCH 1/9] lzo: Add further info to a patch
Date: Wed, 25 May 2022 10:00:02 +0200 [thread overview]
Message-ID: <20220525100002.7d702096@melee> (raw)
In-Reply-To: <20220524152401.1663317-1-ross.burton@arm.com>
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.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-05-25 8:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 15:23 [PATCH 1/9] lzo: Add further info to a patch Ross Burton
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 ` Luca Ceresoli [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=20220525100002.7d702096@melee \
--to=luca.ceresoli@bootlin.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.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