From: Arnd Bergmann <arnd@arndb.de>
To: Doug Ledford <dledford@redhat.com>
Cc: Lijun Ou <oulijun@huawei.com>,
"Wei Hu(Xavier)" <xavier.huwei@huawei.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Hulk Robot <hulkci@huawei.com>,
YueHaibing <yuehaibing@huawei.com>,
Shaobo Xu <xushaobo2@huawei.com>,
Shamir Rabinovitch <shamir.rabinovitch@oracle.com>,
Xi Wang <wangxi11@huawei.com>, Tao Tian <tiantao6@huawei.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/hns: Fix build error again
Date: Mon, 21 Oct 2019 23:51:05 +0200 [thread overview]
Message-ID: <CAK8P3a071AHaN0Jb9dX5c3syQZZPgaR9bX3V3nseDTsPvgDWGg@mail.gmail.com> (raw)
In-Reply-To: <113038cde3f1335ba9bf4d66f22f0a536b70ef1f.camel@redhat.com>
On Mon, Oct 21, 2019 at 11:09 PM Doug Ledford <dledford@redhat.com> wrote:
>
> This fix looks reasonable, but since I can't test this at all, and I'm
> personally tired of trying and failing to fix this issue, I need to ask
> if you've tried all the permutations for this just to confirm it works
> in all valid cases?
I'm fairly sure I would have found them all by now: Since I sent this
patch I built 4680 randconfig kernels, 293 of which had some HNS
driver enabled.
I also like to think that I spent more time to think it through in theory.
Arnd
next prev parent reply other threads:[~2019-10-21 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 21:18 [PATCH] RDMA/hns: Fix build error again Arnd Bergmann
2019-10-21 21:08 ` Doug Ledford
2019-10-21 21:51 ` Arnd Bergmann [this message]
2019-10-22 17:50 ` Doug Ledford
2019-10-29 19:17 ` Jason Gunthorpe
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=CAK8P3a071AHaN0Jb9dX5c3syQZZPgaR9bX3V3nseDTsPvgDWGg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=dledford@redhat.com \
--cc=hulkci@huawei.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=oulijun@huawei.com \
--cc=shamir.rabinovitch@oracle.com \
--cc=tiantao6@huawei.com \
--cc=wangxi11@huawei.com \
--cc=xavier.huwei@huawei.com \
--cc=xushaobo2@huawei.com \
--cc=yamada.masahiro@socionext.com \
--cc=yuehaibing@huawei.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 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.