From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/3] syscalls/pipe2_03: Add new test for pipe2 O_DIRECT flag
Date: Fri, 17 Apr 2020 18:50:58 +0800 [thread overview]
Message-ID: <CAEemH2eVn8BHXaR5bJMjRZy1xOnbNAEMxX2QR2DK=wOAts800w@mail.gmail.com> (raw)
In-Reply-To: <CAEemH2eMVJE0=LwgRVihjTXCm_LYqTHSb4ehPKWzXV_Siou0uA@mail.gmail.com>
On Fri, Apr 17, 2020 at 6:13 PM Li Wang <liwang@redhat.com> wrote:
>
>
> On Fri, Apr 17, 2020 at 5:56 PM Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> wrote:
>
>> Hi Li
>>
>> > Hi Xu,
>> >
>> > I feel confused that is this test duplicated with the one Lanie's
>> > patch2/2? why using the same test name?
>> My pipe2_03.c is to test O_DIRECT flag, Lanie's patch is to test
>> O_NONBLOCK flag as my perivous email said, see[1].
>>
>> I don't think it is a problem(I need to generate patch-set, so named
>> pipe2_03.c is better).
>>
>
> But that will cause git patch confiliction becasue same file name, isn't
> it?
> I'm going to apply Lanie's two patches(modified on the git.v3), and once
> it done, your patch will broken on git confiliction.
>
>
One feasible way is that I help to rename Lanie's pipe2_03.c to pipe2_04.c
and apply the patches first, then you do rebase your codes on the
latest commit. Is that OK for you?
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200417/919bae77/attachment.htm>
next prev parent reply other threads:[~2020-04-17 10:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:52 [LTP] [PATCH] syscalls/pipe2_01: convert into new API Yang Xu
2020-04-15 5:11 ` [LTP] [PATCH v2] " Yang Xu
2020-04-16 7:28 ` [LTP] [PATCH v3 0/3] increase pipe2 coverage Yang Xu
2020-04-16 7:29 ` [LTP] [PATCH v3 1/3] syscalls/pipe2_01: convert into new API Yang Xu
2020-04-21 8:19 ` Li Wang
2020-04-21 8:27 ` Yang Xu
2020-04-16 7:29 ` [LTP] [PATCH v3 2/3] syscalls/pipe2_02: Add new test for pipe2 O_CLOEXEC flag Yang Xu
2020-04-21 8:49 ` Li Wang
2020-04-21 9:41 ` Yang Xu
2020-04-21 9:59 ` Li Wang
2020-04-16 7:29 ` [LTP] [PATCH v3 3/3] syscalls/pipe2_03: Add new test for pipe2 O_DIRECT flag Yang Xu
2020-04-17 9:44 ` Li Wang
2020-04-17 9:56 ` Yang Xu
2020-04-17 10:13 ` Li Wang
2020-04-17 10:50 ` Li Wang [this message]
2020-04-21 9:53 ` Li Wang
2020-04-21 10:21 ` Yang Xu
2020-04-22 6:05 ` Li Wang
2020-04-22 6:14 ` Yang Xu
2020-04-22 7:29 ` Li Wang
2020-04-22 8:08 ` Yang Xu
2020-04-22 8:12 ` Yang Xu
2020-04-22 9:31 ` Yang Xu
2020-04-22 10:05 ` Li Wang
2020-04-22 10:06 ` Yang Xu
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='CAEemH2eVn8BHXaR5bJMjRZy1xOnbNAEMxX2QR2DK=wOAts800w@mail.gmail.com' \
--to=liwang@redhat.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 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.