All of lore.kernel.org
 help / color / mirror / Atom feed
From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] ccache: 4.9.1 -> 4.10
Date: Tue, 11 Jun 2024 20:21:29 -0700	[thread overview]
Message-ID: <cover.1718159460.git.liezhi.yang@windriver.com> (raw)

From: Robert Yang <liezhi.yang@windriver.com>

The fmt is from meta-oe, will send a patch to remove it from meta-oe after this
patch is merged.

// Robert

The following changes since commit 07b4c7a2bd23f8645810e13439e814caaaf9cd94:

  linuxloader: add -armhf on arm only for TARGET_FPU 'hard' (2024-06-11 11:41:09 +0100)

are available in the Git repository at:

  https://github.com/robertlinux/yocto rbt/ccache
  https://github.com/robertlinux/yocto/tree/rbt/ccache

Robert Yang (2):
  ccache: 4.9.1 -> 4.10
  fmt: Add it from meta-oe for ccache 4.10

 meta/conf/distro/include/maintainers.inc      |  1 +
 .../{ccache_4.9.1.bb => ccache_4.10.bb}       | 20 ++++++----
 .../0001-xxhash.h-Fix-build-with-gcc-12.patch | 37 -------------------
 meta/recipes-devtools/fmt/fmt_10.2.1.bb       | 16 ++++++++
 4 files changed, 30 insertions(+), 44 deletions(-)
 rename meta/recipes-devtools/ccache/{ccache_4.9.1.bb => ccache_4.10.bb} (44%)
 delete mode 100644 meta/recipes-devtools/ccache/files/0001-xxhash.h-Fix-build-with-gcc-12.patch
 create mode 100644 meta/recipes-devtools/fmt/fmt_10.2.1.bb

-- 
2.45.1



             reply	other threads:[~2024-06-12  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  3:21 liezhi.yang [this message]
2024-06-12  3:21 ` [PATCH 1/2] ccache: 4.9.1 -> 4.10 liezhi.yang
2024-06-12  3:35   ` Patchtest results for " patchtest
2024-06-12  3:21 ` [PATCH 2/2] fmt: Add it from meta-oe for ccache 4.10 liezhi.yang

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=cover.1718159460.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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.