From: Jason Gunthorpe <jgg@nvidia.com>
To: Gal Pressman <galpress@amazon.com>
Cc: Doug Ledford <dledford@redhat.com>, <linux-rdma@vger.kernel.org>,
Alexander Matushevsky <matua@amazon.com>
Subject: Re: [PATCH for-next 0/5] EFA cleanups 2021-01-26
Date: Thu, 28 Jan 2021 15:58:06 -0400 [thread overview]
Message-ID: <20210128195806.GA135851@nvidia.com> (raw)
In-Reply-To: <20210126120702.9807-1-galpress@amazon.com>
On Tue, Jan 26, 2021 at 02:06:56PM +0200, Gal Pressman wrote:
> Hi,
>
> This series contains misc cleanups to the EFA driver and device
> definitions. Detailed descriptions can be found in the commit messages.
>
> Thanks,
> Gal
>
> Gal Pressman (5):
> RDMA/efa: Remove redundant NULL pointer check of CQE
> RDMA/efa: Remove duplication of upper/lower_32_bits
> RDMA/efa: Remove unnecessary indentation in defs comments
> RDMA/efa: Remove unused 'select' field from get/set feature command
> descriptor
> RDMA/efa: Remove unused syndrome enum values
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-01-28 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 12:06 [PATCH for-next 0/5] EFA cleanups 2021-01-26 Gal Pressman
2021-01-26 12:06 ` [PATCH for-next 1/5] RDMA/efa: Remove redundant NULL pointer check of CQE Gal Pressman
2021-01-26 12:06 ` [PATCH for-next 2/5] RDMA/efa: Remove duplication of upper/lower_32_bits Gal Pressman
2021-01-26 12:06 ` [PATCH for-next 3/5] RDMA/efa: Remove unnecessary indentation in defs comments Gal Pressman
2021-01-26 12:07 ` [PATCH for-next 4/5] RDMA/efa: Remove unused 'select' field from get/set feature command descriptor Gal Pressman
2021-01-26 12:07 ` [PATCH for-next 5/5] RDMA/efa: Remove unused syndrome enum values Gal Pressman
2021-01-28 19:58 ` 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=20210128195806.GA135851@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.