From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Ross Burton" <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org, nd@arm.com
Subject: Re: [OE-core] [PATCH 3/3] sysfstools: don't install to base_libdir
Date: Tue, 20 Jun 2023 15:00:19 +0200 [thread overview]
Message-ID: <20230620150019.14645e48@booty> (raw)
In-Reply-To: <20230620123404.3854578-3-ross.burton@arm.com>
Hi Ross,
On Tue, 20 Jun 2023 13:34:04 +0100
"Ross Burton" <ross.burton@arm.com> wrote:
> From: Ross Burton <ross.burton@arm.com>
I guess the Subject line should s/sysfstools/sysfsutils/, so I fixed
that locally for my AB testing branch.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-06-20 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 12:34 [PATCH 1/3] sysfsutils: fetch a supported fork from github ross.burton
2023-06-20 12:34 ` [PATCH 2/3] sysfsutils: update 2.1.0 -> 2.1.1 ross.burton
2023-06-20 12:34 ` [PATCH 3/3] sysfstools: don't install to base_libdir ross.burton
2023-06-20 13: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=20230620150019.14645e48@booty \
--to=luca.ceresoli@bootlin.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.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