From: Leon Romanovsky <leon@kernel.org>
To: "Latecki, Karol" <karol.latecki@intel.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Honggang Li <honli@redhat.com>,
Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.de>,
Benjamin Drung <benjamin.drung@ionos.com>
Subject: Re: Question about v37 and v38 minor releases
Date: Thu, 24 Mar 2022 16:45:33 +0200 [thread overview]
Message-ID: <YjyEDYtw7Rrf2JfB@unreal> (raw)
In-Reply-To: <DM4PR11MB55494BCEA81DCEB6FED81834E7119@DM4PR11MB5549.namprd11.prod.outlook.com>
On Wed, Mar 16, 2022 at 09:34:19AM +0000, Latecki, Karol wrote:
> Hello!
>
> I would like to ask if there are any plans or ETAs for rdma-core v37 and v38 minor release? Our team is waiting for 4c905646de3e75bdccada4abe9f0d273d76eaf50 "mlx5: Initialize wr_data when post a work request" to be upstreamed to package repositories like yum or dnf.
Usually request to create stable branch comes from package managers itself.
RedHat - Honggang Li <honli@redhat.com>
SuSE - Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.de>
Debian - Benjamin Drung <benjamin.drung@ionos.com>
They manage rdma-core packages in relevant package repositories.
Thanks
> Apologies for low-importance question, but I did not find any road map or other communication channel on rdma-core github site.
>
> Thank you!
> Karol Latecki
next prev parent reply other threads:[~2022-03-24 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM4PR11MB5549E169E3C06766D347A936E7119@DM4PR11MB5549.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB55492CF07DCC8105204D39AFE7119@DM4PR11MB5549.namprd11.prod.outlook.com>
2022-03-16 9:34 ` Question about v37 and v38 minor releases Latecki, Karol
2022-03-24 14:45 ` Leon Romanovsky [this message]
2022-03-24 16:53 ` Nicolas Morey-Chaisemartin
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=YjyEDYtw7Rrf2JfB@unreal \
--to=leon@kernel.org \
--cc=benjamin.drung@ionos.com \
--cc=honli@redhat.com \
--cc=karol.latecki@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=nmoreychaisemartin@suse.de \
/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