From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: pgowda cve <pgowda.cve@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Randy MacLeod <rwmacleod@gmail.com>,
umesh.kalappa0@gmail.com
Subject: Re: [OE-core] [PATCH v2] state/staging: Fix directory not deleted for race
Date: Mon, 18 Oct 2021 16:59:09 +0200 [thread overview]
Message-ID: <CA+chaQc15i3WztOeZqCXK923YEg4_+VZnAsb2MXmnSQwyccJjg@mail.gmail.com> (raw)
In-Reply-To: <6149502653526ba43975b86936e6aa74415c9ac0.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Mon, Oct 18, 2021 at 4:52 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Mon, 2021-10-18 at 19:17 +0530, pgowda cve wrote:
> > Hi Richard,
> >
> > Thanks for the review and suggestion.
> >
> > > > I'm wondering if we should just add TCLIBC to PN unconditionally?
> >
> > I didn't want to add TCLIBC to the code when using default GLIBC.
> > Hence, I tried to keep the folder default for GLIBC.
> >
> > However, if you suggest adding TCLIBC to PN unconditionally;
> > I will modify the patch and submit.
>
> Lets try that please.
>
> There is a related issue Martin reported where the recipe is really
> TUNE_ARCH
> specific and not really TARGET_ARCH specific. One step at a time I guess
> though.
>
I think you were referring to:
https://lists.openembedded.org/g/openembedded-core/message/156516
and it's currently even MACHINE_ARCH due to poking in MACHINEOVERRIDES
variable, but in theory it should be possible to re-write the logic to be
only TUNE_ARCH specific.
Cheers,
[-- Attachment #2: Type: text/html, Size: 1522 bytes --]
next prev parent reply other threads:[~2021-10-18 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 11:46 [PATCH] state/staging: Fix directory not deleted for race Pgowda
2021-09-16 7:45 ` Richard Purdie
[not found] ` <16A53DBD300C0C8E.4388@lists.openembedded.org>
2021-09-16 7:53 ` [OE-core] " Richard Purdie
2021-09-16 8:28 ` Pgowda
2021-09-28 15:12 ` Randy MacLeod
2021-09-28 20:21 ` Richard Purdie
2021-10-01 7:24 ` [PATCH v2] " Pgowda
2021-10-18 12:53 ` Richard Purdie
2021-10-18 13:47 ` pgowda cve
2021-10-18 14:52 ` Richard Purdie
2021-10-18 14:59 ` Martin Jansa [this message]
2021-10-19 4:43 ` pgowda cve
2021-10-01 7:28 ` [OE-core] [PATCH] " pgowda cve
[not found] ` <16A9D78EAA10C9CD.7289@lists.openembedded.org>
2021-10-18 7:43 ` pgowda cve
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=CA+chaQc15i3WztOeZqCXK923YEg4_+VZnAsb2MXmnSQwyccJjg@mail.gmail.com \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rwmacleod@gmail.com \
--cc=umesh.kalappa0@gmail.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 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.