All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Michal Marek <mmarek@suse.com>
Cc: Nicholas Piggin <npiggin@gmail.com>, linux-kbuild@vger.kernel.org
Subject: [PATCH 0/2] kbuild: thin archives and gc-sections updates
Date: Tue,  1 Nov 2016 12:56:12 +1100	[thread overview]
Message-ID: <20161101015614.1546-1-npiggin@gmail.com> (raw)

Hi,

Here are a couple of updates for the new build processes. I think
these could go in 4.9 because nobody has started using them seriously
yet, but on the other hand that is also a reason they can probably
wait until 4.10.

Thanks,
Nick

Nicholas Piggin (2):
  kbuild: thin archives for multi-y targets
  kbuild: keep data tables through dead code elimination

 include/asm-generic/vmlinux.lds.h | 68 +++++++++++++++++++--------------------
 scripts/Makefile.build            | 13 ++++++--
 2 files changed, 44 insertions(+), 37 deletions(-)

-- 
2.9.3


             reply	other threads:[~2016-11-01  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01  1:56 Nicholas Piggin [this message]
2016-11-01  1:56 ` [PATCH 1/2] kbuild: thin archives for multi-y targets Nicholas Piggin
2016-11-01  1:56 ` [PATCH 2/2] kbuild: keep data tables through dead code elimination Nicholas Piggin

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=20161101015614.1546-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.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 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.