From: Jens Axboe <[email protected]>
To: Jackie Liu <[email protected]>, liming wu <[email protected]>
Cc: [email protected]
Subject: Re: delete unneeded int-type
Date: Fri, 29 Nov 2019 09:21:41 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/29/19 12:25 AM, Jackie Liu wrote:
> 2019年11月29日 16:19,liming wu <[email protected]> 写道:
>>
>> Hi
>>
>> It can't buid successfully except use c99.
>>
>>
>> Subject: [PATCH] delete unneede int-type
>>
>> ---
>> test/accept-link.c | 2 +-
>> test/poll-link.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/test/accept-link.c b/test/accept-link.c
>> index 2fbc12e..91dbc2b 100644
>> --- a/test/accept-link.c
>> +++ b/test/accept-link.c
>> @@ -131,7 +131,7 @@ void *recv_thread(void *arg)
>>
>> assert(io_uring_submit(&ring) == 2);
>>
>> - for (int i = 0; i < 2; i++) {
>> + for (i = 0; i < 2; i++) {
>> struct io_uring_cqe *cqe;
>> int idx;
>>
>> diff --git a/test/poll-link.c b/test/poll-link.c
>> index 3cc2ca7..abddb71 100644
>> --- a/test/poll-link.c
>> +++ b/test/poll-link.c
>> @@ -127,7 +127,7 @@ void *recv_thread(void *arg)
>>
>> assert(io_uring_submit(&ring) == 2);
>>
>> - for (int i = 0; i < 2; i++) {
>> + for (i = 0; i < 2; i++) {
>> struct io_uring_cqe *cqe;
>> int idx;
>>
>> --
>> <delete-unneede-int-type.patch>
>
> I think it would be better for you to send patches using git send-email
> instead of using attachments.
Yeah, this one is small enough that I just hand apply it, but the
patches are clearly mangled.
--
Jens Axboe
next prev parent reply other threads:[~2019-11-29 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 8:19 delete unneeded int-type liming wu
2019-11-29 8:25 ` Jackie Liu
2019-11-29 17:21 ` Jens Axboe [this message]
2019-11-29 17:18 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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