From: Jason Gunthorpe <jgg@nvidia.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 0/5] RDMA kernel patches for kernel v5.14
Date: Fri, 28 May 2021 20:23:29 -0300 [thread overview]
Message-ID: <20210528232329.GA3852821@nvidia.com> (raw)
In-Reply-To: <20210524041211.9480-1-bvanassche@acm.org>
On Sun, May 23, 2021 at 09:12:06PM -0700, Bart Van Assche wrote:
> Hi Jason,
>
> Please consider the five patches in this series for kernel v5.14.
>
> Thanks,
>
> Bart.
>
> Changes compared to v1:
> - Reworked patch 1/5 based on Leon's feedback.
> - Changed __packed into __packed __aligned(4) in patch 3/5.
> - Removed the mr_list variable in patch 4/5.
> - Removed one if-test from patch 5/5.
>
> Bart Van Assche (5):
> IB/hfi1: Move a function from a header file into a .c file
> RDMA/srp: Add more structure size checks
> RDMA/srp: Apply the __packed attribute to members instead of
> structures
> RDMA/srp: Fix a recently introduced memory leak
> RDMA/srp: Make struct scsi_cmnd and struct srp_request adjacent
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-05-28 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 4:12 [PATCH v2 0/5] RDMA kernel patches for kernel v5.14 Bart Van Assche
2021-05-24 4:12 ` [PATCH v2 1/5] IB/hfi1: Move a function from a header file into a .c file Bart Van Assche
2021-05-24 4:12 ` [PATCH v2 2/5] RDMA/srp: Add more structure size checks Bart Van Assche
2021-05-24 4:12 ` [PATCH v2 3/5] RDMA/srp: Apply the __packed attribute to members instead of structures Bart Van Assche
2021-05-24 4:12 ` [PATCH v2 4/5] RDMA/srp: Fix a recently introduced memory leak Bart Van Assche
2021-05-24 4:12 ` [PATCH v2 5/5] RDMA/srp: Make struct scsi_cmnd and struct srp_request adjacent Bart Van Assche
2021-05-28 23:23 ` 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=20210528232329.GA3852821@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox