From: Nicholas Piggin <npiggin@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-arch@vger.kernel.org, linux-kbuild@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] kbuild: provide THIN_ARCHIVES option for all architectures
Date: Tue, 30 May 2017 00:34:34 +1000 [thread overview]
Message-ID: <20170530003434.5099e7b3@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20170529203355.4ebd1062@canb.auug.org.au>
On Mon, 29 May 2017 20:33:55 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Nick,
>
> On Mon, 29 May 2017 18:11:03 +1000 Nicholas Piggin <npiggin@gmail.com> wrote:
> >
> > diff --git a/arch/Kconfig b/arch/Kconfig
> > index 6c00e5b00f8b..28e64cb65dd5 100644
> > --- a/arch/Kconfig
> > +++ b/arch/Kconfig
> > @@ -511,10 +511,23 @@ config CC_STACKPROTECTOR_STRONG
> > endchoice
> >
> > config THIN_ARCHIVES
> > - bool
> > + bool "Build the kernel using thin archives"
> > + default n
>
> Of course, this will be enabled by allmodconfig, etc builds ...
>
Yes that is true. Thanks for making a note of it -- I guess the
changelog could be interpreted as implying no change to any
existing build without arch enablement. I didn't intend to mislead
there.
Thanks,
Nick
next prev parent reply other threads:[~2017-05-29 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 8:11 [PATCH] kbuild: provide THIN_ARCHIVES option for all architectures Nicholas Piggin
2017-05-29 10:33 ` Stephen Rothwell
2017-05-29 14:34 ` Nicholas Piggin [this message]
2017-05-29 17:03 ` Linus Torvalds
2017-05-29 17:14 ` Linus Torvalds
2017-05-29 23:13 ` Nicholas Piggin
2017-05-30 3:22 ` Linus Torvalds
2017-05-30 3:55 ` Nicholas Piggin
2017-05-30 3:54 ` Linus Torvalds
2017-05-29 18:52 ` Sam Ravnborg
2017-05-29 23:49 ` Nicholas Piggin
2017-05-31 21:13 ` Arnd Bergmann
2017-06-04 23:17 ` Masahiro Yamada
2017-06-05 7:00 ` 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=20170530003434.5099e7b3@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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