From: Doug Ledford <dledford@redhat.com>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Kaike Wan <kaike.wan@intel.com>
Subject: Re: [PATCH for-rc 2/2] IB/hfi1: Use a common pad buffer for 9B and 16B packets
Date: Thu, 17 Oct 2019 16:34:42 -0400 [thread overview]
Message-ID: <fa266ca5e309a69f6d0762d88a8d1c13f93847b0.camel@redhat.com> (raw)
In-Reply-To: <20191004204934.26838.13099.stgit@awfm-01.aw.intel.com>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Fri, 2019-10-04 at 16:49 -0400, Dennis Dalessandro wrote:
> From: Mike Marciniszyn <mike.marciniszyn@intel.com>
>
> There is no reason for a different pad buffer for the two
> packet types.
>
> Expand the current buffer allocation to allow for both
> packet types.
>
> Fixes: f8195f3b14a0 ("IB/hfi1: Eliminate allocation while atomic")
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Reviewed-by: Kaike Wan <kaike.wan@intel.com>
> Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
> Signed-off-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
Thanks, applied to for-rc.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-17 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 20:40 [PATCH for-rc 0/2] Updates for 5.4 rc cycle Dennis Dalessandro
2019-10-04 20:40 ` [PATCH for-rc 1/2] IB/hfi1: Avoid excessive retry for TID RDMA READ request Dennis Dalessandro
2019-10-17 20:34 ` Doug Ledford
2019-10-04 20:49 ` [PATCH for-rc 2/2] IB/hfi1: Use a common pad buffer for 9B and 16B packets Dennis Dalessandro
2019-10-04 20:51 ` Dennis Dalessandro
2019-10-17 20:34 ` Doug Ledford [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=fa266ca5e309a69f6d0762d88a8d1c13f93847b0.camel@redhat.com \
--to=dledford@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dennis.dalessandro@intel.com \
--cc=jgg@ziepe.ca \
--cc=kaike.wan@intel.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;
as well as URLs for NNTP newsgroup(s).