From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Doug Ledford <dledford@redhat.com>,
Adit Ranadive <aditr@vmware.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Faisal Latif <faisal.latif@intel.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>,
Potnuri Bharat Teja <bharat@chelsio.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
VMware PV-Drivers <pv-drivers@vmware.com>
Subject: Re: [PATCH rdma-next 0/2] Spring cleanup
Date: Mon, 22 Mar 2021 16:12:34 +0200 [thread overview]
Message-ID: <YFil0nfFgSSh0mXb@unreal> (raw)
In-Reply-To: <20210322130012.GA247894@nvidia.com>
On Mon, Mar 22, 2021 at 10:00:12AM -0300, Jason Gunthorpe wrote:
> On Sun, Mar 14, 2021 at 03:39:06PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > Bunch of cleanup in RDMA subsystem.
> >
> > Leon Romanovsky (2):
> > RDMA: Fix kernel-doc compilation warnings
> > RDMA: Delete not-used static inline functions
>
> Applied to for-next
>
> How did you find the unused static inline functions?
Accidentally spotted such in pvrdma and later wrote one liner to create
me a list of functions to delete.
Thanks
>
> Thanks,
> Jason
next prev parent reply other threads:[~2021-03-22 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 13:39 [PATCH rdma-next 0/2] Spring cleanup Leon Romanovsky
2021-03-14 13:39 ` [PATCH rdma-next 1/2] RDMA: Fix kernel-doc compilation warnings Leon Romanovsky
2021-03-14 13:39 ` [PATCH rdma-next 2/2] RDMA: Delete not-used static inline functions Leon Romanovsky
2021-03-22 13:00 ` [PATCH rdma-next 0/2] Spring cleanup Jason Gunthorpe
2021-03-22 14:12 ` Leon Romanovsky [this message]
2021-03-22 18:03 ` Adit Ranadive
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=YFil0nfFgSSh0mXb@unreal \
--to=leon@kernel.org \
--cc=aditr@vmware.com \
--cc=bharat@chelsio.com \
--cc=bmt@zurich.ibm.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=pv-drivers@vmware.com \
--cc=shiraz.saleem@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 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.