From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>, Igor Stoppa <igor.stoppa@gmail.com>
Cc: Faisal Latif <faisal.latif@intel.com>,
Igor Stoppa <igor.stoppa@huawei.com>,
Chien Tung <chien.tin.tung@intel.com>,
Roland Dreier <rolandd@cisco.com>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] infiniband: nes: add unlikely() to assert()
Date: Fri, 07 Sep 2018 11:13:21 -0400 [thread overview]
Message-ID: <811a6feca9fdea2db59ac392a4711cd897f46cc7.camel@redhat.com> (raw)
In-Reply-To: <20180905060106.GI2977@mtr-leonro.mtl.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Wed, 2018-09-05 at 09:01 +0300, Leon Romanovsky wrote:
> On Fri, Aug 31, 2018 at 10:24:18PM +0300, Igor Stoppa wrote:
> > Typically the assert is expected to not fail.
>
> This whole assert can be removed.
>
> >
> > Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
> > Acked-by: Doug Ledford <dledford@redhat.com>
>
> Most probably that I missed discussion, but anyway, does this
> "Acked-by" come from internal or external discussion?
This patch was part of a larger series on lkml. In that context, I
acked it so that the series could be applied by whomever took it (it
didn't belong on rdma-list as a series since only one patch out of some
large number touched rdma files). Now it is being resent as not part of
a series, but my ack was preserved.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-07 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 19:24 Igor Stoppa
2018-09-05 6:01 ` Leon Romanovsky
2018-09-05 18:54 ` Igor Stoppa
2018-09-07 15:13 ` Doug Ledford [this message]
2018-09-07 15:25 ` Igor Stoppa
2018-09-07 17:31 ` Leon Romanovsky
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=811a6feca9fdea2db59ac392a4711cd897f46cc7.camel@redhat.com \
--to=dledford@redhat.com \
--cc=chien.tin.tung@intel.com \
--cc=faisal.latif@intel.com \
--cc=igor.stoppa@gmail.com \
--cc=igor.stoppa@huawei.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rolandd@cisco.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
all inboxes | Powered by JetHome®