From: Arnd Bergmann <arnd@arndb.de>
To: Mark Charlebois <charlebm@gmail.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <mmarek@suse.com>,
Nicholas Piggin <npiggin@gmail.com>,
Namhyung Kim <namhyung.with.foss@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [SUBMITTED 20170314] [v333kbuild: disable -ffunction-sections on gcc-4.7 with ftrace
Date: Fri, 31 Mar 2017 22:39:13 +0200 [thread overview]
Message-ID: <CAK8P3a0W8q_6Kbm64U501zmbTonx_1g4euSLZS=4rJ5sVnhhfw@mail.gmail.com> (raw)
In-Reply-To: <CAFzeTN3-=a6n-PEKP5ssCUszYYPu5R5_6uf9DEdptPKEuWOsrQ@mail.gmail.com>
On Fri, Mar 31, 2017 at 5:54 PM, Mark Charlebois <charlebm@gmail.com> wrote:
> What is it you need from me? To rebase 03497934e21, test (on what ARCH) and
> resend (to who)?. Let me know if Arnd forwarding the patch isn't sufficient.
> I'm not set up to test this at the moment, but could if needed.
I've just send it, I think that's sufficient and will keep the the
patch attributed
correctly.
Arnd
prev parent reply other threads:[~2017-03-31 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 21:33 [PATCH] [v2] kbuild: disable -ffunction-sections on gcc-4.7 with ftrace Arnd Bergmann
2017-03-14 21:35 ` [PATCH] [v333kbuild: " Arnd Bergmann
2017-03-14 21:37 ` [PATCH] [SUBMITTED 20170314] " Arnd Bergmann
2017-03-29 2:07 ` Masahiro Yamada
2017-03-29 9:30 ` Arnd Bergmann
2017-03-30 15:42 ` Masahiro Yamada
2017-03-31 8:48 ` Arnd Bergmann
[not found] ` <CAFzeTN3-=a6n-PEKP5ssCUszYYPu5R5_6uf9DEdptPKEuWOsrQ@mail.gmail.com>
2017-03-31 20:39 ` Arnd Bergmann [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='CAK8P3a0W8q_6Kbm64U501zmbTonx_1g4euSLZS=4rJ5sVnhhfw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=charlebm@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=namhyung.with.foss@gmail.com \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.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.