From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Or Gerlitz' <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: 'Matan Barak'
<matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
'linux-rdma' <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
'Majd Dibbiny' <majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
'Hariprasad Shenai'
<hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: RE: [PATCH V1] IB/cma: Fix RDMA port validation for iWarp
Date: Thu, 14 Jan 2016 09:08:15 -0600 [thread overview]
Message-ID: <005501d14edd$649859a0$2dc90ce0$@opengridcomputing.com> (raw)
In-Reply-To: <5697B80E.5090903-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> -----Original Message-----
> From: Or Gerlitz [mailto:ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org]
> Sent: Thursday, January 14, 2016 9:01 AM
> To: Steve Wise
> Cc: 'Matan Barak'; dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org; 'linux-rdma'; 'Majd Dibbiny'; 'Hariprasad Shenai'
> Subject: Re: [PATCH V1] IB/cma: Fix RDMA port validation for iWarp
>
> On 1/14/2016 4:53 PM, Steve Wise wrote:
> > Hey Or, iWARP is non-functional in 4.4, and this patch fixes the regression. I suggest we get this fix in stable asap.
>
> sure, we can make an exception in our usual track for this one, but you
> need upstream commit ID ## -- Doug is your key person here
This patch commit comment cites the offending patch:
Fixes: abae1b71dd37 ('IB/cma: cma_validate_port should verify the port
and netdevice')
Does that need to be in the Cc: line somehow?
Doug?
--
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
next prev parent reply other threads:[~2016-01-14 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:19 [PATCH V1] IB/cma: Fix RDMA port validation for iWarp Matan Barak
[not found] ` <1452158369-2938-1-git-send-email-matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-01-07 17:38 ` Steve Wise
2016-01-12 18:43 ` Steve Wise
2016-01-13 10:32 ` Matan Barak
[not found] ` <CAAKD3BAWUfg6sVLCEtb-vBrC9kGtVYO784xg4_tGqiZaOVh-2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-13 15:03 ` Steve Wise
2016-01-14 7:14 ` Or Gerlitz
[not found] ` <56974AEE.6060201-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-01-14 14:53 ` Steve Wise
2016-01-14 15:00 ` Or Gerlitz
[not found] ` <5697B80E.5090903-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-01-14 15:08 ` Steve Wise [this message]
2016-01-14 17:40 ` Leon Romanovsky
[not found] ` <20160114174014.GA30615-2ukJVAZIZ/Y@public.gmane.org>
2016-01-15 19:47 ` Steve Wise
[not found] ` <56994CE2.1060205-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2016-01-19 18:44 ` Doug Ledford
[not found] ` <569E8402.2080001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-01-19 18:52 ` Steve Wise
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='005501d14edd$649859a0$2dc90ce0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).