From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Daniel Jurgens <danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next] IB/core: Only maintain real QPs in the security lists
Date: Tue, 7 Nov 2017 10:31:35 -0700 [thread overview]
Message-ID: <20171107173135.GC7063@ziepe.ca> (raw)
In-Reply-To: <20171107171026.GN18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
On Tue, Nov 07, 2017 at 07:10:26PM +0200, Leon Romanovsky wrote:
> We will send followup patch to clean it, but for this patch I prefer do
> not change the logic here because it is supposed to go to stable@.
Yep
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Daniel Jurgens <danielj@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH rdma-next] IB/core: Only maintain real QPs in the security lists
Date: Tue, 7 Nov 2017 10:31:35 -0700 [thread overview]
Message-ID: <20171107173135.GC7063@ziepe.ca> (raw)
In-Reply-To: <20171107171026.GN18825@mtr-leonro.local>
On Tue, Nov 07, 2017 at 07:10:26PM +0200, Leon Romanovsky wrote:
> We will send followup patch to clean it, but for this patch I prefer do
> not change the logic here because it is supposed to go to stable@.
Yep
Jason
next prev parent reply other threads:[~2017-11-07 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:33 [PATCH rdma-next] IB/core: Only maintain real QPs in the security lists Leon Romanovsky
2017-11-07 16:33 ` Leon Romanovsky
[not found] ` <20171107163326.23881-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-07 16:46 ` Jason Gunthorpe
2017-11-07 16:46 ` Jason Gunthorpe
2017-11-07 16:52 ` Daniel Jurgens
[not found] ` <065e66ff-e901-bd5c-674d-173eab720989-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-07 16:55 ` Jason Gunthorpe
2017-11-07 16:55 ` Jason Gunthorpe
[not found] ` <20171107165539.GB7063-uk2M96/98Pc@public.gmane.org>
2017-11-07 17:10 ` Leon Romanovsky
2017-11-07 17:10 ` Leon Romanovsky
[not found] ` <20171107171026.GN18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-07 17:31 ` Jason Gunthorpe [this message]
2017-11-07 17:31 ` Jason Gunthorpe
2017-11-07 17:15 ` Daniel Jurgens
[not found] ` <87a902ae-351b-43c4-4a42-b362c981a767-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-07 17:32 ` Jason Gunthorpe
2017-11-07 17:32 ` Jason Gunthorpe
2017-11-07 18:40 ` Leon Romanovsky
2017-11-13 21:24 ` Doug Ledford
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=20171107173135.GC7063@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.