linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yanjun <zyjzyj2000@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next v2 0/3] Three rxe bug fixes
Date: Wed, 4 Aug 2021 09:39:04 +0800	[thread overview]
Message-ID: <CAD=hENc0QMKKHcK+XTTq6TRJHOab-8GvY6e=a5sPDQMH1NbyGg@mail.gmail.com> (raw)
In-Reply-To: <20210803155814.GC2886223@nvidia.com>

On Tue, Aug 3, 2021 at 11:58 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> On Thu, Jul 29, 2021 at 05:00:37PM -0500, Bob Pearson wrote:
> > These patches fix three bugs currently in the rxe driver.
> > One of these was released earlier. In this v2 version two other bug
> > fixes are added.
> >
> > Bob Pearson (3):
> >   RDMA/rxe: Fix bug in get_srq_wqe() in rxe_resp.c
> >   RDMA/rxe: Fix bug in rxe_net.c
>
> I fixed these up and applied them to for-rc

I will focus on the other 2 commits except the commit "RDMA/rxe: Fix
bug in rxe_net.c" since this commit is reviewed and tested.

Zhu Yanjun

>
> Please be careful that the fixes lines are correct and subjects should
> be self descriptive not 'fix a bug in x'
>
> >   RDMA/rxe: Add memory barriers to kernel queues
>
> This one can go to for-next
>
> Jason

      reply	other threads:[~2021-08-04  1:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 22:00 [PATCH for-next v2 0/3] Three rxe bug fixes Bob Pearson
2021-07-29 22:00 ` [PATCH for-next v2 1/3] RDMA/rxe: Fix bug in get_srq_wqe() in rxe_resp.c Bob Pearson
2021-07-29 22:00 ` [PATCH for-next v2 2/3] RDMA/rxe: Fix bug in rxe_net.c Bob Pearson
2021-08-02  8:33   ` Zhu Yanjun
2021-07-29 22:00 ` [PATCH for-next v2 3/3] RDMA/rxe: Add memory barriers to kernel queues Bob Pearson
2021-08-03 15:58 ` [PATCH for-next v2 0/3] Three rxe bug fixes Jason Gunthorpe
2021-08-04  1:39   ` Zhu Yanjun [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='CAD=hENc0QMKKHcK+XTTq6TRJHOab-8GvY6e=a5sPDQMH1NbyGg@mail.gmail.com' \
    --to=zyjzyj2000@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).