From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>,
linux-rdma@vger.kernel.org, yanjun.zhu@linux.dev,
"yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"y-goto@fujitsu.com" <y-goto@fujitsu.com>
Subject: rxe patches
Date: Thu, 10 Nov 2022 15:44:13 -0400 [thread overview]
Message-ID: <Y21Ujbxz+B56hMjY@nvidia.com> (raw)
I am looking at the patchworks here:
https://patchwork.kernel.org/project/linux-rd
And all I see is a huge number of rxe patches with no Reviewed-bys.
I need all of you in the rxe community to start looking at these. At a
minimum group test these things. The changes are too big to expect me
to deeply understand rxe (which I do not) and somehow approve them.
If this does not improve I will probably propose Bob as the maintainer
of RXE and just take everything he sends, unreviewed by me.
Thanks,
Jason
next reply other threads:[~2022-11-10 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:44 Jason Gunthorpe [this message]
2022-11-11 1:40 ` rxe patches Yanjun Zhu
2022-11-11 5:36 ` lizhijian
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=Y21Ujbxz+B56hMjY@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=y-goto@fujitsu.com \
--cc=yangx.jy@fujitsu.com \
--cc=yanjun.zhu@linux.dev \
/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