All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Bruce Ashfield" <bruce.ashfield@gmail.com>,
	"Köry Maincent" <kory.maincent@bootlin.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/6] perf: fix reproducibility issues
Date: Wed, 10 Mar 2021 13:58:31 +0000	[thread overview]
Message-ID: <8d673369cf2afb9a9c4eb0c7178525b1d11e5913.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4PFwiJM+TBiC3457jNa-GOtiGYa3-g9iy7DKCAcsfyK8g@mail.gmail.com>

On Wed, 2021-03-10 at 08:37 -0500, Bruce Ashfield wrote:
> I'm unfortunately out of time on this, so obviously this can be
> dropped and I'll work on it again for next release.

I'll merge it since this is an incremental improvement, I just won't drop
perf from the exclusion list yet. Its a great step forward, I think
there is some remaining linking order issue lurking somewhere.

Cheers,

Richard



  reply	other threads:[~2021-03-10 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 19:23 [PATCH 0/6] kernel: consolidated pull request Bruce Ashfield
2021-03-09 19:23 ` [PATCH 1/6] perf: fix reproducibility issues Bruce Ashfield
2021-03-10 10:42   ` [OE-core] " Kory Maincent
2021-03-10 11:27     ` Kory Maincent
2021-03-10 13:37     ` Bruce Ashfield
2021-03-10 13:58       ` Richard Purdie [this message]
2021-03-09 19:23 ` [PATCH 2/6] reproducibile: remove perf from exclusions Bruce Ashfield
2021-03-09 19:26   ` Bruce Ashfield
2021-03-09 19:23 ` [PATCH 3/6] linux-yocto/5.10: update to v5.10.21 Bruce Ashfield
2021-03-10 10:32   ` [OE-core] " Kory Maincent
2021-03-10 13:35     ` Bruce Ashfield
2021-03-09 19:23 ` [PATCH 4/6] linux-yocto/5.4: update to v5.4.103 Bruce Ashfield
2021-03-09 19:23 ` [PATCH 5/6] linux-yocto/qemuarmv5: fix configuration warning Bruce Ashfield
2021-03-09 19:23 ` [PATCH 6/6] kern-tools: symbol-why fix and README update Bruce Ashfield

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=8d673369cf2afb9a9c4eb0c7178525b1d11e5913.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=kory.maincent@bootlin.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 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.