All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "niko.mauno@vaisala.com via lists.openembedded.org"
	<niko.mauno=vaisala.com@lists.openembedded.org>
Cc: niko.mauno@vaisala.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] strace: Drop redundant oe_runmake parameter
Date: Fri, 24 Jun 2022 12:30:54 +0200	[thread overview]
Message-ID: <20220624123054.0f8ee472@booty> (raw)
In-Reply-To: <d12df769-ced9-c31d-e3fb-e07858c852a1@vaisala.com>

Hi Niko,

On Thu, 23 Jun 2022 19:53:58 +0300
"niko.mauno@vaisala.com via lists.openembedded.org"
<niko.mauno=vaisala.com@lists.openembedded.org> wrote:

> On 6/23/22 12:30, Luca Ceresoli via lists.openembedded.org wrote:
> > Unfortunately this patch does not apply as strace has been bumped to
> > 5.18 by a recent commit. Could you send a v2 series with this updated
> > please?  
> 
> Hi Luca, new v2 series sent with updated strace version: 
> https://patchwork.yoctoproject.org/project/oe-core/list/?series=5032

Thank you. Yesterday I had already picked patches 1 and 3 for testing
on the autobuilders and all builds succeeded. I'm taking your v2 for my
next testing run today.

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-06-24 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:16 [PATCH 1/3] ptest.bbclass: Honor PARALLEL_MAKE, PARALLEL_MAKEINST Niko Mauno
2022-06-22 19:16 ` [PATCH 2/3] strace: Drop redundant oe_runmake parameter Niko Mauno
2022-06-23  9:30   ` [OE-core] " Luca Ceresoli
2022-06-23 16:53     ` Niko Mauno
2022-06-24 10:30       ` Luca Ceresoli [this message]
2022-06-22 19:16 ` [PATCH 3/3] valgrind: " Niko Mauno
2022-06-25 16:55 ` [OE-core] [PATCH 1/3] ptest.bbclass: Honor PARALLEL_MAKE, PARALLEL_MAKEINST Richard Purdie

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=20220624123054.0f8ee472@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=niko.mauno=vaisala.com@lists.openembedded.org \
    --cc=niko.mauno@vaisala.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.