From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] topology: delete output file if parsing fails.
Date: Mon, 12 Jun 2017 18:44:08 +0100 [thread overview]
Message-ID: <1497289448.30929.237.camel@loki> (raw)
In-Reply-To: <s5h7f0k2nil.wl-tiwai@suse.de>
On Sat, 2017-06-10 at 11:35 +0200, Takashi Iwai wrote:
> On Fri, 09 Jun 2017 17:33:42 +0200,
> Liam Girdwood wrote:
> >
> > Currently the binary output file is left when parsing fails. This confuses
> > GNU Make if the parsing fails and causes the compilation to partially
> > complete.
> >
> > Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
>
> Applied, thanks.
>
> But at the next time, please specify which repo to apply.
> It took some time until I figured out it's for alsa-utils.
Apologies, I was doing some alsa-lib patches at the same time. This did
make me realize we do have some other similar named areas that overlap
in the kernel and in alsa-lib, but they are probably manageable for the
moment.
Thanks
Liam
prev parent reply other threads:[~2017-06-12 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:33 [PATCH] topology: delete output file if parsing fails Liam Girdwood
2017-06-10 9:35 ` Takashi Iwai
2017-06-12 17:44 ` Liam Girdwood [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=1497289448.30929.237.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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).