All of lore.kernel.org
 help / color / mirror / Atom feed
From: pgowda cve <pgowda.cve@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
	Randy MacLeod <rwmacleod@gmail.com>,
	umesh.kalappa0@gmail.com
Subject: Re: [PATCH v2] state/staging: Fix directory not deleted for race
Date: Tue, 19 Oct 2021 10:13:30 +0530	[thread overview]
Message-ID: <CALY49870-f=DUMMaO4aEJ_7qx=413+vR46kgbrqzvPbwuUJe3A@mail.gmail.com> (raw)
In-Reply-To: <6149502653526ba43975b86936e6aa74415c9ac0.camel@linuxfoundation.org>

Hi Richard,

Thanks for the confirmation.

>> Let's try that please.

Please find the patch posted at the following link as per your suggestion.
https://lists.openembedded.org/g/openembedded-core/message/157103

>> There is a related issue Martin reported where the recipe is really TUNE_ARCH
>> specific and not really TARGET_ARCH specific.

I will check this issue.


Thanks,
pgowda


  parent reply	other threads:[~2021-10-19  4:43 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                 ` [OE-core] " Martin Jansa
2021-10-19  4:43                 ` pgowda cve [this message]
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='CALY49870-f=DUMMaO4aEJ_7qx=413+vR46kgbrqzvPbwuUJe3A@mail.gmail.com' \
    --to=pgowda.cve@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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.