From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>,
Hongxu Jia <hongxu.jia@windriver.com>
Subject: Re: [OE-core] [PATCH 01/14] python3: drop unneeded multiprocessing module patch
Date: Mon, 10 Jan 2022 14:23:17 +0000 [thread overview]
Message-ID: <043d4b73d9234292da52175adf6f59483920ced5.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8sah0ehNNcvQqfO9hJaCLq6jx72gpTbqz2cUyLQSdstg@mail.gmail.com>
On Mon, 2022-01-10 at 15:21 +0100, Alexander Kanavin wrote:
> On Mon, 10 Jan 2022 at 14:59, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > Isn't this now working since pthread was merged into the main libc library
> > and
> > therefore separate linking for pthread is no longer needed?
> >
>
>
> Yes, there was a previous discussion with the same point, so this needs a
> commit message adjustment?
Please as I worry someone would try and backport it with the wrong reasoning.
Cheers,
Richard
prev parent reply other threads:[~2022-01-10 14:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 22:27 [PATCH 01/14] python3: drop unneeded multiprocessing module patch Alexander Kanavin
2022-01-09 22:27 ` [PATCH 02/14] ruby: disable rdoc due to non-reproducibility Alexander Kanavin
2022-01-09 22:27 ` [PATCH 03/14] rust-llvm: apply the same reproducibility patch as for llvm proper Alexander Kanavin
2022-01-09 22:27 ` [PATCH 04/14] busybox: update 1.34.1 -> 1.35.0 Alexander Kanavin
2022-01-10 15:09 ` [OE-core] " akuster808
[not found] ` <16C8F145D420B770.27414@lists.openembedded.org>
2022-01-10 15:10 ` Armin Kuster
2022-01-09 22:27 ` [PATCH 05/14] systemd: update 249.7 -> 250.1 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 06/14] python3-numpy: update 1.21.4 -> 1.22.0 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 07/14] mdadm: update 4.1 -> 4.2 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 08/14] librsvg: update 2.52.4 -> 2.52.5 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 09/14] libportal: update 0.4 -> 0.5 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 10/14] epiphany: make libportal optional, and move it to meta-oe Alexander Kanavin
2022-01-10 18:43 ` [OE-core] " Khem Raj
2022-01-10 18:49 ` Alexander Kanavin
2022-01-10 18:57 ` Khem Raj
2022-01-10 19:18 ` Alexander Kanavin
2022-01-10 20:54 ` Khem Raj
2022-01-11 7:49 ` Khem Raj
2022-01-11 8:48 ` Alexander Kanavin
2022-01-11 19:44 ` Khem Raj
2022-01-09 22:27 ` [PATCH 11/14] qemuboot/runqemu: fully form the ip= kernel parameter Alexander Kanavin
2022-01-09 22:27 ` [PATCH 12/14] parselogs: add a couple systemd false positives Alexander Kanavin
2022-01-09 22:27 ` [PATCH 13/14] connman: do nothing in qemu, do not touch eth0 Alexander Kanavin
2022-01-11 10:54 ` [OE-core] " Richard Purdie
2022-01-11 11:02 ` Alexander Kanavin
2022-01-11 11:08 ` Richard Purdie
2022-01-11 11:10 ` Alexander Kanavin
2022-01-11 11:15 ` Richard Purdie
2022-01-09 22:27 ` [PATCH 14/14] systemd-boot: restore reproducibility Alexander Kanavin
2022-01-10 13:59 ` [OE-core] [PATCH 01/14] python3: drop unneeded multiprocessing module patch Richard Purdie
2022-01-10 14:21 ` Alexander Kanavin
2022-01-10 14:23 ` 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=043d4b73d9234292da52175adf6f59483920ced5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=hongxu.jia@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox