From: Christoph Lameter <cl@linux.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leon@kernel.org>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] Fix: Remove racy Subnet Manager sendonly join checks
Date: Thu, 28 Jan 2021 14:34:45 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2101281433270.10563@www.lameter.com> (raw)
In-Reply-To: <20210128140335.GA13699@nvidia.com>
On Thu, 28 Jan 2021, Jason Gunthorpe wrote:
> I need patches to be sent in a way that shows in patchworks to be
> applied:
>
> https://patchwork.kernel.org/project/linux-rdma/list/
I see it in patchworks:
https://patchwork.kernel.org/project/linux-rdma/patch/alpine.DEB.2.22.394.2101251126090.344695@www.lameter.com/
> > Index: linux/drivers/infiniband/core/cma.c
> > ===================================================================
> > +++ linux/drivers/infiniband/core/cma.c 2021-01-25 09:39:29.191032891 +0000
> > @@ -4542,17 +4542,6 @@ static int cma_join_ib_multicast(struct
>
> Also if patches aren't generated with 'git diff' then I won't fix any
> minor conflicts :(
Well it was quilt ...... Do I need to put it into a git tree somewhere?
next prev parent reply other threads:[~2021-01-28 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:28 [PATCH] Fix: Remove racy Subnet Manager sendonly join checks Christoph Lameter
2021-01-25 11:44 ` Leon Romanovsky
2021-01-28 14:03 ` Jason Gunthorpe
2021-01-28 14:21 ` Leon Romanovsky
2021-01-28 14:34 ` Christoph Lameter [this message]
2021-01-28 14:44 ` Jason Gunthorpe
2021-01-28 14:58 ` Christoph Lameter
2021-01-28 18:11 ` Jason Gunthorpe
[not found] <alpine.DEB.2.22.394.2101281845160.13303@www.lameter.com>
2021-02-09 19:15 ` Jason Gunthorpe
2021-02-10 9:31 ` Christoph Lameter
2021-02-10 13:03 ` Jason Gunthorpe
2021-02-10 18:51 ` Christoph Lameter
2021-02-12 22:16 ` Dennis Dalessandro
2021-02-12 22:13 ` Dennis Dalessandro
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=alpine.DEB.2.22.394.2101281433270.10563@www.lameter.com \
--to=cl@linux.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--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 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.