Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Anuj Mittal <anuj.mittal@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v6 1/2] ltp: Update to 20200120
Date: Sat, 29 Feb 2020 17:53:43 +0100	[thread overview]
Message-ID: <20200229165343.GA832653@x230> (raw)
In-Reply-To: <c9d181ea-ebc6-1183-73dc-461f601c2799@intel.com>

Hi Khem, Anuj,

> > * 0002-kernel-controllers-Link-with-libfts-explicitly-on-mu.patch
> > IMHO this one shouldn't be needed not, but CI still fails without it
Khem, thanks for fixing it! It'd take me long time.

> Is this patch still needed after the change in v6?
I've sent v7 where I removed it. It actually wasn't used, because although I put
the file itself back in v5 (+ it was in v6 from Khem), it wasn't actually listed
in SRC_URI, so I expect it wasn't used.

Kind regards,
Petr


      reply	other threads:[~2020-02-29 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 15:00 [PATCH v6 1/2] ltp: Update to 20200120 Khem Raj
2020-02-29 15:00 ` [PATCH v6 2/2] ltp: Remove mips related open_posix_testsuite patch Khem Raj
2020-02-29 15:30 ` [PATCH v6 1/2] ltp: Update to 20200120 Anuj Mittal
2020-02-29 16:53   ` Petr Vorel [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=20200229165343.GA832653@x230 \
    --to=petr.vorel@gmail.com \
    --cc=anuj.mittal@intel.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