From: wangxin (CQ) <wangxin410@huawei.com>
To: ltp@lists.linux.it
Subject: [LTP] 答复: [PATCH] openposix/conformance/interfaces: Correct typos
Date: Wed, 14 Apr 2021 08:48:23 +0000 [thread overview]
Message-ID: <1e332d4428ea42aeb59e1173b654ce30@huawei.com> (raw)
In-Reply-To: <CAEemH2dU2r8gFS5r3os7UwXFUEmmPqR9CnAizXbP_FHP+Evd+A@mail.gmail.com>
Hi Wang,
I think I see what you mean. I'll submit a new patch to the community later.
Thank you for the advice.
--
Regards,
Wang Xin
???: Li Wang [mailto:liwang@redhat.com]
????: 2021?4?14? 16:27
???: wangxin (CQ) <wangxin410@huawei.com>
??: LTP List <ltp@lists.linux.it>
??: Re: [LTP] [PATCH] openposix/conformance/interfaces: Correct typos
Hi Xin,
On Wed, Apr 14, 2021 at 4:16 PM wangxin (CQ) <wangxin410@huawei.com<mailto:wangxin410@huawei.com>> wrote:
Hi Wang,
Thanks so much for your review!
I just re-checked the latest code and found that the code needed to be modified was not the same as the last time.
Therefore, do you want to incorporate the patch submitted last time?
If there is a conflict, I can modify the patch submitted last time.
Feel free to make a new patch as you want, I don't insist on the previous version.
Just guarantee to rebase on the latest LTP is fine.
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210414/37fca914/attachment.htm>
next prev parent reply other threads:[~2021-04-14 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 3:20 [LTP] [PATCH] openposix/conformance/interfaces: Correct typos Wang Xin
2021-04-14 6:57 ` Li Wang
2021-04-14 8:15 ` [LTP] 答复: " wangxin
2021-04-14 8:26 ` [LTP] " Li Wang
2021-04-14 8:48 ` wangxin [this message]
2021-04-14 9:47 ` Li Wang
2021-04-15 2:11 ` [LTP] 答复: " wangxin
2021-04-15 2:19 ` [LTP] " Li Wang
-- strict thread matches above, loose matches on Subject: below --
2021-04-27 2:51 Wang Xin
2021-04-27 19:20 ` Petr Vorel
2021-04-28 3:26 ` [LTP] 答复: " wangxin
2021-04-28 5:57 ` Petr Vorel
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=1e332d4428ea42aeb59e1173b654ce30@huawei.com \
--to=wangxin410@huawei.com \
--cc=ltp@lists.linux.it \
/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