public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Ficet <jean-vincent.ficet-BUmcmmAb0Fc@public.gmane.org>
To: Hal Rosenstock
	<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	"ira.weiny" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH infiniband-diags] Add Bull device ID support to device white lists
Date: Fri, 9 Dec 2016 15:29:58 +0100	[thread overview]
Message-ID: <584ABFE6.4070902@atos.net> (raw)
In-Reply-To: <703b953b-7165-72d1-3c1e-c3b1f8c54f28-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>

Hello,

On 12/09/2016 03:15 PM, Hal Rosenstock wrote:
> On 12/9/2016 5:32 AM, Vincent Ficet wrote:
>> Hello,
>>
>> The patch proposed by Hal Rosenstock does not list all Bull device IDs.
>>
>> Please apply the attached patch which contains an up to date list of such IDs.
> Would it be better to combine Bull Switch-IB and Switch-IB2 ranges into
> one check rather than keeping them separate as the device IDs are
> contiguous ?
I just wanted to separate SwitchIB and SwitchIB2 for clarity, but we can gather them if you wish to do so.

Which option do you prefer, together or split ?
>
> Also, looks like similar change should also be done in
> ibdiag_common.c:is_mlnx_ext_port_info_supported.
Thanks for pointing this. I'll fix it too, but first I need you to answer the question just above.

Best Regards,

Vincent
>
> -- Hal
>
>> Best Regards,
>>
>> Vincent

--
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:[~2016-12-09 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 19:22 [PATCH infiniband-diags] Add Bull device ID support to device white lists Hal Rosenstock
     [not found] ` <e5ad4256-53fe-9ecc-f880-89347134ec42-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-12-07 14:53   ` ira.weiny
     [not found]     ` <20161207145338.GD24724-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2016-12-09 10:32       ` Vincent Ficet
     [not found]         ` <584A8823.4070506-BUmcmmAb0Fc@public.gmane.org>
2016-12-09 14:15           ` Hal Rosenstock
     [not found]             ` <703b953b-7165-72d1-3c1e-c3b1f8c54f28-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-12-09 14:29               ` Vincent Ficet [this message]
     [not found]                 ` <584ABFE6.4070902-BUmcmmAb0Fc@public.gmane.org>
2016-12-09 14:40                   ` Hal Rosenstock
     [not found]                     ` <46fac349-4687-961a-4d63-697064f391da-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-12-19  7:10                       ` Weiny, Ira
     [not found]                         ` <2807E5FD2F6FDA4886F6618EAC48510E3C611A58-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-12-19  8:44                           ` Vincent Ficet
     [not found]                             ` <58579DFD.2040206-BUmcmmAb0Fc@public.gmane.org>
2016-12-20 16:56                               ` ira.weiny

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=584ABFE6.4070902@atos.net \
    --to=jean-vincent.ficet-bumcmmab0fc@public.gmane.org \
    --cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox