From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ibacm: Close MAD port when umad_register fails
Date: Wed, 20 Sep 2017 16:50:12 -0600 [thread overview]
Message-ID: <20170920225012.GC20974@obsidianresearch.com> (raw)
In-Reply-To: <20170920223030.GA11703@yuvallap>
On Thu, Sep 21, 2017 at 01:30:30AM +0300, Yuval Shaia wrote:
> On Mon, Sep 18, 2017 at 03:55:47PM -0600, Jason Gunthorpe wrote:
> > On Tue, Sep 19, 2017 at 12:51:58AM +0300, Yuval Shaia wrote:
> > > Cleanup of the open port is needed when program fails to register MAD
> > > port.
> > >
> > > Signed-off-by: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> > > ibacm/src/acm.c | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > Yuval, can you send this patch against rdma-core please? ibacm is not
> > longer separate.
> >
> > https://github.com/linux-rdma/rdma-core
>
> You mean as PR to rdma-core or just that subject should say rdma-core?
> (or both?)
Yes both/either will help it get picked up.
When I looked at the patch I wondered if it may have been against the
original pre-rdma-core ibacm tree, since it didn't mention rdma-core
or cc a rdma-core maintainer.... but I guess the ibacm/srcm/acm.c path
means it is against rdma-core, right?
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
next prev parent reply other threads:[~2017-09-20 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 21:51 [PATCH] ibacm: Close MAD port when umad_register fails Yuval Shaia
[not found] ` <20170918215158.27597-1-yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-09-18 21:55 ` Jason Gunthorpe
[not found] ` <20170918215547.GB17476-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-20 22:30 ` Yuval Shaia
2017-09-20 22:50 ` Jason Gunthorpe [this message]
[not found] ` <20170920225012.GC20974-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-20 22:53 ` Yuval Shaia
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=20170920225012.GC20974@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@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