All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chandramouli, Dasaratharaman" <dasaratharaman.chandramouli-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Don Hiatt <don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Ira Weiny <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 0/7] Add support for OPA classport info
Date: Fri, 28 Apr 2017 11:47:09 -0700	[thread overview]
Message-ID: <9a061845-2a2f-3c19-08b3-00a9ddab8292@intel.com> (raw)
In-Reply-To: <1493403017.3041.166.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>



On 4/28/2017 11:10 AM, Doug Ledford wrote:
> On Mon, 2017-03-20 at 19:38 -0400, Dasaratharaman Chandramouli wrote:
>> This series moves the classport info query initiation and update
>> from callers such as ipoib to the ib_sa module itself. The classport
>> info cache is updated whenever ib_sa receives an appropriate state
>> change event.
>>
>> Since classport info is only used to check if sendonly full member
>> support
>> is enabled by the SM, we expose a function
>> ib_sa_sendonly_fullmem_support
>> that can be called to check if the support is enabled.
>>
>> Additionally, we introduce support for opa classport info. These are
>> defined specifically for OPA devices and expose additional features
>> in the
>> capability mask bits along with longer LID sizes in some of the other
>> fields.
>>
>> Patch 1 to 3 fix checkpatch issues (1 issue type per patch) on two
>> functions that patch 4 then moves around. Patch 5 makes changes
>> to implicitly query and cache classport info. Patch 6 adds
>> verbs capability API for core layers to query and find out if they
>> are running on an OPA device. Finally, patch 7 adds OPA classport
>> info
>> query support.
>
> I took patches 1-6 of this series.  However, I need you to rebase patch
> 7 against my current k.o/for-4.12-rdma-netdevice branch as there are
> significant conflicts between this and the VNIC patches I've already
> taken.
>

Hi Doug -- I pulled your for-4.12-rdma-netdevice and tried to apply 
patch 7. I see no conflicts. It compiled cleanly as well. May be i am 
missing something here. Just want to make sure i have the same branch as 
yours.
Is this your commit at the HEAD currently?

commit 94d595c56077fd8b0f61701e03fd4b3dc8c62038
Author: Dasaratharaman Chandramouli <dasaratharaman.chandramouli-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date:   Mon Mar 20 19:38:09 2017 -0400

     IB/core: Add rdma_cap_opa_ah to expose opa address handles


Thanks,
Dasa
--
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

  parent reply	other threads:[~2017-04-28 18:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 23:38 [PATCH v2 0/7] Add support for OPA classport info Dasaratharaman Chandramouli
     [not found] ` <1490053090-32840-1-git-send-email-dasaratharaman.chandramouli-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-20 23:38   ` [PATCH v2 1/7] IB/SA: Fix lines longer than 80 columns Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 2/7] IB/SA: Add braces when using sizeof Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 3/7] IB/SA: Remove unwanted braces Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 4/7] IB/SA: Move functions update_sm_ah() and ib_sa_event() Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 5/7] IB/SA: Modify SA to implicitly cache Class Port info Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 6/7] IB/core: Add rdma_cap_opa_ah to expose opa address handles Dasaratharaman Chandramouli
2017-03-20 23:38   ` [PATCH v2 7/7] IB/SA: Add support to query opa classport info Dasaratharaman Chandramouli
2017-04-14 23:32   ` [PATCH v2 0/7] Add support for OPA " Chandramouli, Dasaratharaman
2017-04-28 18:10   ` Doug Ledford
     [not found]     ` <1493403017.3041.166.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-28 18:47       ` Chandramouli, Dasaratharaman [this message]
     [not found]         ` <9a061845-2a2f-3c19-08b3-00a9ddab8292-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-04-28 19:23           ` Chandramouli, Dasaratharaman
     [not found]             ` <b6f3caf1-7558-1291-b361-ac58932d10ae-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-04-28 22:15               ` Doug Ledford
     [not found]                 ` <1493417741.3041.171.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-28 23:35                   ` Chandramouli, Dasaratharaman
     [not found]                     ` <07556307-eea5-5571-66d7-90be9abebba0-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-04-28 23:46                       ` Chandramouli, Dasaratharaman
     [not found]                         ` <05c8bb91-7291-4cda-6299-5f6061ef635e-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-04-29 18:49                           ` Chandramouli, Dasaratharaman

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=9a061845-2a2f-3c19-08b3-00a9ddab8292@intel.com \
    --to=dasaratharaman.chandramouli-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=don.hiatt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-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.