From: Jason Gunthorpe <jgg@nvidia.com>
To: Allen Pais <allen.lkml@gmail.com>
Cc: <dledford@redhat.com>, <linux-rdma@vger.kernel.org>,
<selvin.xavier@broadcom.com>, <devesh.sharma@broadcom.com>,
<somnath.kotur@broadcom.com>,
<sriharsha.basavapatna@broadcom.com>,
<nareshkumar.pbs@broadcom.com>, <mike.marciniszyn@intel.com>,
<dennis.dalessandro@intel.com>, <faisal.latif@intel.com>,
<shiraz.saleem@intel.com>
Subject: Re: [PATCH v2 0/5] RDMA: convert tasklets to use new
Date: Thu, 3 Sep 2020 12:06:09 -0300 [thread overview]
Message-ID: <20200903150609.GA1569719@nvidia.com> (raw)
In-Reply-To: <20200903060637.424458-1-allen.lkml@gmail.com>
On Thu, Sep 03, 2020 at 11:36:32AM +0530, Allen Pais wrote:
> commit 12cc923f1ccc ("tasklet: Introduce new initialization API")'
> introduced a new tasklet initialization API. This series converts
> all the infiniband drivers to use the new tasklet_setup() API
>
> The series is based on 5.9-rc3
>
> v2:
> Fixed bnxt_re driver. Suggested by Jason.
> Fixed subject line.
>
> Allen Pais (5):
> RDMA/bnxt_re: convert tasklets to use new tasklet_setup() API
> IB/hfi1: convert tasklets to use new tasklet_setup() API
> RDMA/i40iw: convert tasklets to use new tasklet_setup() API
> RDMA/qib: convert tasklets to use new tasklet_setup() API
> RDMA/rxe: convert tasklets to use new tasklet_setup() API
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-09-03 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 6:06 [PATCH v2 0/5] RDMA: convert tasklets to use new Allen Pais
2020-09-03 6:06 ` [PATCH v2 1/5] RDMA/bnxt_re: convert tasklets to use new tasklet_setup() API Allen Pais
2020-09-03 6:06 ` [PATCH v2 2/5] IB/hfi1: " Allen Pais
2020-09-03 6:06 ` [PATCH v2 3/5] RDMA/i40iw: " Allen Pais
2020-09-03 6:06 ` [PATCH v2 4/5] RDMA/qib: " Allen Pais
2020-09-03 6:06 ` [PATCH v2 5/5] RDMA/rxe: " Allen Pais
2020-09-03 15:06 ` 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=20200903150609.GA1569719@nvidia.com \
--to=jgg@nvidia.com \
--cc=allen.lkml@gmail.com \
--cc=dennis.dalessandro@intel.com \
--cc=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=nareshkumar.pbs@broadcom.com \
--cc=selvin.xavier@broadcom.com \
--cc=shiraz.saleem@intel.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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.