From: Andi Kleen <andi@firstfloor.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>, Dirk Gouders <dirk@gouders.net>
Subject: Re: [PATCH 1/2] kbuild: Support split debug info v4
Date: Wed, 30 Jul 2014 20:44:36 +0200 [thread overview]
Message-ID: <20140730184436.GM18735@two.firstfloor.org> (raw)
In-Reply-To: <53D8F816.7040104@suse.cz>
> The failure mode with ccache is that the *.dwo files are not stored, but
> the build proceeds, right? This is at least what I'm seeing. I'm just
That's right.
> wondering if the config option should be inverted to make
> all{yes,mod}config builds happy. But it's probably not necessary if the
> build passes.
Ok I'll not change it then and only resend the other patch.
-Andi
prev parent reply other threads:[~2014-07-30 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 23:11 [PATCH 1/2] kbuild: Support split debug info v4 Andi Kleen
2014-07-29 23:11 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen
2014-07-30 13:38 ` Michal Marek
2014-07-30 13:50 ` [PATCH 1/2] kbuild: Support split debug info v4 Michal Marek
2014-07-30 18:44 ` Andi Kleen [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=20140730184436.GM18735@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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