From: Jens Axboe <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
io-uring <[email protected]>,
Pavel Begunkov <[email protected]>,
gwml <[email protected]>
Subject: Re: [PATCH liburing v3 0/4] Changes for Makefile
Date: Thu, 10 Mar 2022 05:14:25 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 10 Mar 2022 11:12:27 +0000, Alviro Iskandar Setiawan wrote:
> This patchset (v3) changes Makefile. 4 patches here:
>
> 1. Remove -fomit-frame-pointer flag, because it's already covered
> by the -O2 optimization flag.
>
> 2. When the header files are modified, the compiled objects are
> not going to be recompiled because the header files are not
> marked as a dependency for the objects.
>
> [...]
Applied, thanks!
[1/4] src/Makefile: Remove `-fomit-frame-pointer` from default build
commit: de214792d38700ba470a560cf3729a9bd62acb35
[2/4] src/Makefile: Add header files as dependency
commit: 9ea9df11bbdbbf3bceae38679dd175b092950142
[3/4] test/Makefile: Add liburing.a as a dependency
commit: b48d6af787c00fd4a8f3614f8c1a0443a3054eef
[4/4] examples/Makefile: Add liburing.a as a dependency
commit: 115cca320dd4df9293440d8e410bebb064822265
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-03-10 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:12 [PATCH liburing v3 0/4] Changes for Makefile Alviro Iskandar Setiawan
2022-03-10 11:12 ` [PATCH liburing v3 1/4] src/Makefile: Remove `-fomit-frame-pointer` from default build Alviro Iskandar Setiawan
2022-03-10 11:12 ` [PATCH liburing v3 2/4] src/Makefile: Add header files as dependency Alviro Iskandar Setiawan
2022-03-10 11:12 ` [PATCH liburing v3 3/4] test/Makefile: Add liburing.a as a dependency Alviro Iskandar Setiawan
2022-03-10 11:12 ` [PATCH liburing v3 4/4] examples/Makefile: " Alviro Iskandar Setiawan
2022-03-10 11:40 ` [PATCH liburing v3 0/4] Changes for Makefile Ammar Faizi
2022-03-10 12:14 ` Jens Axboe [this message]
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=164691446560.8573.18148443232651092454.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[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