From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Lijun Ou <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core] libhns: Update the size and member order of hns_roce_create_qp structure
Date: Sat, 30 Sep 2017 09:45:18 -0600 [thread overview]
Message-ID: <20170930154518.GA14152@obsidianresearch.com> (raw)
In-Reply-To: <1506761477-47350-1-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Sat, Sep 30, 2017 at 04:51:17PM +0800, Lijun Ou wrote:
> In order to keep the size and member order with the
> hns_roce_ib_create_qp sturcture of the kernel driver,
> it need to update hns_roce_create_qp's structure
> members. Otherwise, it will run fail.
What?
Did you break the uapi? What kernel patch does this match with?
Generally structs in the u_abi.h headers cannot be changed like this.
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-30 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 8:51 [PATCH rdma-core] libhns: Update the size and member order of hns_roce_create_qp structure Lijun Ou
[not found] ` <1506761477-47350-1-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-09-30 15:45 ` Jason Gunthorpe [this message]
[not found] ` <20170930154518.GA14152-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-30 16:05 ` Leon Romanovsky
[not found] ` <20170930160515.GG2965-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-30 16:07 ` Leon Romanovsky
2017-09-30 16:29 ` Jason Gunthorpe
[not found] ` <20170930162953.GA15393-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-10-01 5:28 ` Leon Romanovsky
2017-10-01 14:39 ` Wei Hu (Xavier)
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=20170930154518.GA14152@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oulijun-hv44wF8Li93QT0dZR+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 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.