From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org,
Steve Wise <swise@opengridcomputing.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] IB/srpt: Increase port count
Date: Mon, 14 May 2018 05:03:28 -0700 [thread overview]
Message-ID: <20180514120328.GA5081@infradead.org> (raw)
In-Reply-To: <20180510223209.10277-1-bart.vanassche@wdc.com>
On Thu, May 10, 2018 at 03:32:09PM -0700, Bart Van Assche wrote:
> Since there are adapters that have four ports, increase the size of
> the srpt_device.port[] array. This patch avoids that the following
> warning is hit with quad port Chelsio adapters:
>
> WARN_ON(sdev->device->phys_port_cnt > ARRAY_SIZE(sdev->port));
Should we add a IB_MAX_PORTS define that ULPs can rely on in the core?
next prev parent reply other threads:[~2018-05-14 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 22:32 [PATCH] IB/srpt: Increase port count Bart Van Assche
2018-05-14 12:03 ` Christoph Hellwig [this message]
2018-05-14 14:23 ` Bart Van Assche
2018-05-14 14:24 ` hch
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=20180514120328.GA5081@infradead.org \
--to=hch@infradead.org \
--cc=bart.vanassche@wdc.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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