From: Pavel Machek <pavel@ucw.cz>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: switch to thin archives
Date: Sun, 18 Jun 2017 12:04:26 +0200 [thread overview]
Message-ID: <20170618100426.GB20211@amd> (raw)
In-Reply-To: <20170602125454.13304-1-npiggin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Fri 2017-06-02 22:54:54, Nicholas Piggin wrote:
> Switch from incremental build to thin archives for packaging built-in.o.
> binutils version must be bumped to 2.20. Proposed patch for 4.13.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
You should explain any advantage this is supposed to have.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-06-18 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 12:54 [PATCH] kbuild: switch to thin archives Nicholas Piggin
2017-06-02 20:57 ` kbuild test robot
2017-06-02 20:57 ` kbuild test robot
2017-06-03 6:51 ` Nicholas Piggin
2017-06-18 10:04 ` Pavel Machek [this message]
2017-06-19 7:45 ` Nicholas Piggin
2017-06-19 9:15 ` Pavel Machek
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=20170618100426.GB20211@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox