From: Michal Marek <mmarek@suse.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
Nicholas Piggin <npiggin@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Segher Boessenkool <segher@kernel.crashing.org>,
Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections
Date: Fri, 9 Sep 2016 12:59:59 +0200 [thread overview]
Message-ID: <57D2962F.5090200@suse.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1609082016180.14769@knanqh.ubzr>
Dne 9.9.2016 v 02:23 Nicolas Pitre napsal(a):
> On Wed, 24 Aug 2016, Nicholas Piggin wrote:
>
>> Hi Michal,
>>
>> I ended up deciding to do a v3, because I had several changes
>> accumulated, as described in patches.
>
> What is the prospect of those patches going upstream?
>
> I ask because I didn't see them in the kbuild repo yet, nor in next for
> that matter.
I merged the patches into the kbuild.git repository now.
Michal
next prev parent reply other threads:[~2016-09-09 11:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 12:29 [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections Nicholas Piggin
2016-08-24 12:29 ` Nicholas Piggin
2016-08-24 12:29 ` [PATCH 1/3] kbuild: allow architectures to use thin archives instead of ld -r Nicholas Piggin
2016-08-24 12:29 ` [PATCH 2/3] kbuild: allow archs to select link dead code/data elimination Nicholas Piggin
2016-08-24 12:29 ` [PATCH 3/3] kbuild: add arch specific post-link Makefile Nicholas Piggin
2016-08-24 12:29 ` Nicholas Piggin
2016-08-24 13:32 ` Nicholas Piggin
2016-08-24 13:06 ` [PATCH 0/3 v3] kbuild changes, thin archives, --gc-sections Arnd Bergmann
2016-08-24 13:06 ` Arnd Bergmann
2016-08-24 15:13 ` Nicolas Pitre
2016-08-24 14:21 ` David Howells
2016-08-24 14:21 ` David Howells
2016-08-24 15:21 ` Nicolas Pitre
2016-08-24 15:21 ` Nicolas Pitre
2016-08-25 2:56 ` Nicholas Piggin
2016-08-25 2:56 ` Nicholas Piggin
2016-09-09 0:23 ` Nicolas Pitre
2016-09-09 0:23 ` Nicolas Pitre
2016-09-09 10:59 ` Michal Marek [this message]
2016-09-10 4:05 ` Nicolas Pitre
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=57D2962F.5090200@suse.com \
--to=mmarek@suse.com \
--cc=amodra@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=npiggin@gmail.com \
--cc=sam@ravnborg.org \
--cc=segher@kernel.crashing.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).