From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mike Marciniszyn <mike.marciniszyn@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 0/6] More 5.3 patches
Date: Mon, 22 Jul 2019 15:03:19 -0300 [thread overview]
Message-ID: <20190722180319.GA13959@ziepe.ca> (raw)
In-Reply-To: <20190715164423.74174.4994.stgit@awfm-01.aw.intel.com>
On Mon, Jul 15, 2019 at 12:45:14PM -0400, Mike Marciniszyn wrote:
> The following series contains fixes and a cleanup.
>
> I noticed that 5.3 rc1 hasn't happened yet? So I'm not quite sure of
> the destination here.
>
> 5 of the patches are stable, and should be held for the rc or pulled for 5.3.
>
> Deleting the unused define can wait if necessary.
>
>
> John Fleck (1):
> IB/hfi1: Check for error on call to alloc_rsm_map_table
>
> Kaike Wan (4):
> IB/hfi1: Unreserve a flushed OPFN request
> IB/hfi1: Field not zero-ed when allocating TID flow memory
> IB/hfi1: Drop all TID RDMA READ RESP packets after r_next_psn
These four look OK for -rc, applied
> IB/hfi1: Do not update hcrc for a KDETH packet during fault injection
This looks like it is just debugging fixing, it can go to -next
So all 6 applied
Thanks,
Jason
prev parent reply other threads:[~2019-07-22 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 16:45 [PATCH 0/6] More 5.3 patches Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 1/6] IB/hfi1: Check for error on call to alloc_rsm_map_table Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 2/6] IB/hfi1: Unreserve a flushed OPFN request Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 3/6] IB/hfi1: Field not zero-ed when allocating TID flow memory Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 4/6] IB/hfi1: Drop all TID RDMA READ RESP packets after r_next_psn Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 5/6] IB/hfi1: Do not update hcrc for a KDETH packet during fault injection Mike Marciniszyn
2019-07-15 16:45 ` [PATCH 6/6] IB/hfi1: Remove unused define Mike Marciniszyn
2019-07-15 17:54 ` [PATCH 0/6] More 5.3 patches Jason Gunthorpe
2019-07-15 17:55 ` Marciniszyn, Mike
2019-07-15 18:04 ` Jason Gunthorpe
2019-07-15 18:05 ` Marciniszyn, Mike
2019-07-22 18:03 ` Jason Gunthorpe [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=20190722180319.GA13959@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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