From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-networking] [PATCH] rdma-core: upgrade 39.0 -> 40.0
Date: Thu, 14 Apr 2022 10:33:43 +0800 [thread overview]
Message-ID: <1649903624-17790-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1649903624-17790-1-git-send-email-wangmy@fujitsu.com>
Changelog:
https://github.com/linux-rdma/rdma-core/releases/tag/v40.0
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../rdma-core/{rdma-core_39.0.bb => rdma-core_40.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-networking/recipes-support/rdma-core/{rdma-core_39.0.bb => rdma-core_40.0.bb} (95%)
diff --git a/meta-networking/recipes-support/rdma-core/rdma-core_39.0.bb b/meta-networking/recipes-support/rdma-core/rdma-core_40.0.bb
similarity index 95%
rename from meta-networking/recipes-support/rdma-core/rdma-core_39.0.bb
rename to meta-networking/recipes-support/rdma-core/rdma-core_40.0.bb
index 5fb72c7acb..c567e3314b 100644
--- a/meta-networking/recipes-support/rdma-core/rdma-core_39.0.bb
+++ b/meta-networking/recipes-support/rdma-core/rdma-core_40.0.bb
@@ -6,7 +6,7 @@ DEPENDS = "libnl"
RDEPENDS:${PN} = "bash perl"
SRC_URI = "git://github.com/linux-rdma/rdma-core.git;branch=master;protocol=https"
-SRCREV = "b2fedc4b1b891afd2c26ebfd21f9e440e83c28ff"
+SRCREV = "a3e69268892bbd5ab30123748e89a26509a25ac5"
S = "${WORKDIR}/git"
#Default Dual License https://github.com/linux-rdma/rdma-core/blob/master/COPYING.md
--
2.25.1
next prev parent reply other threads:[~2022-04-14 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 2:33 [oe] [meta-oe] [PATCH] qpdf: upgrade 10.5.0 -> 10.6.3 Wang Mingyu
2022-04-14 2:33 ` Wang Mingyu [this message]
2022-04-14 2:33 ` [oe] [meta-oe] [PATCH] s-nail: upgrade 14.9.23 -> 14.9.24 Wang Mingyu
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=1649903624-17790-2-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-devel@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.