From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: jinpu.wang@ionos.com, jgg@ziepe.ca, leon@kernel.org,
linux-rdma@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH V2 3/3] RDMA/rtrs-clt: Kill xchg_paths
Date: Thu, 8 Sep 2022 18:04:17 +0800 [thread overview]
Message-ID: <be6fca6f-d8a6-660e-dc19-14bac7a8df10@linux.dev> (raw)
In-Reply-To: <CAJpMwyjzEc0hLbq7x5nQDPGp5Bwaqp4nTwcNBFryW28jKm8+aw@mail.gmail.com>
On 9/8/22 5:55 PM, Haris Iqbal wrote:
> On Thu, Sep 8, 2022 at 11:46 AM Guoqing Jiang<guoqing.jiang@linux.dev> wrote:
>> Let's call try_cmpxchg directly for the same purpose.
>>
>> Acked-by: Md Haris Iqbal<haris.iqbal@ionos.com>
>> Signed-off-by: Guoqing Jiang<guoqing.jiang@linux.dev>
>> Reported-by: kernel test robot<lkp@intel.com>
> I am not sure whats the correct way of using this. But technically,
> this change was NOT done due to a report from the "kernel test robot".
> It only pointed out the problem in the original patch. To the branch
> maintainers, if its okay to keep this in this scenario, then ignore
> this comment.
Me either, just want to give credit to lkp for previous report, but not sure
if there is a better tag.
Thanks,
Guoqing
next prev parent reply other threads:[~2022-09-08 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 9:45 [PATCH V2 0/3] misc changes for rtrs Guoqing Jiang
2022-09-08 9:45 ` [PATCH V2 1/3] RDMA/rtrs: Update comments for MAX_SESS_QUEUE_DEPTH Guoqing Jiang
2022-09-08 9:45 ` [PATCH V2 2/3] RDMA/rtrs-clt: Break the loop once one path is connected Guoqing Jiang
2022-09-08 9:45 ` [PATCH V2 3/3] RDMA/rtrs-clt: Kill xchg_paths Guoqing Jiang
2022-09-08 9:55 ` Haris Iqbal
2022-09-08 10:04 ` Guoqing Jiang [this message]
2022-09-09 14:15 ` Santosh Pradhan
2022-09-20 12:04 ` [PATCH V2 0/3] misc changes for rtrs Leon Romanovsky
2022-09-20 16:48 ` 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=be6fca6f-d8a6-660e-dc19-14bac7a8df10@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.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.