From: Michal Marek <mmarek@suse.com>
To: Kieran Bingham <kieran@kbingham.co.uk>
Cc: linux-kbuild@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Lee Jones <lee.jones@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dependency issue through subdir's
Date: Mon, 25 Jan 2016 17:25:13 +0100 [thread overview]
Message-ID: <56A64C69.7090000@suse.com> (raw)
In-Reply-To: <56A64BE2.9030105@kbingham.co.uk>
On 2016-01-25 17:22, Kieran Bingham wrote:
> I've got a working patch now for the $(MAKE) version,
> however I've had to use $(build)=scripts/gdb/linux build_constants to
> make it work.
$(build)= is the correct syntax, sorry for the confusion.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Marek <mmarek@suse.com>
To: Kieran Bingham <kieran@ksquared.org.uk>
Cc: linux-kbuild@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Lee Jones <lee.jones@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dependency issue through subdir's
Date: Mon, 25 Jan 2016 17:25:13 +0100 [thread overview]
Message-ID: <56A64C69.7090000@suse.com> (raw)
In-Reply-To: <56A64BE2.9030105@kbingham.co.uk>
On 2016-01-25 17:22, Kieran Bingham wrote:
> I've got a working patch now for the $(MAKE) version,
> however I've had to use $(build)=scripts/gdb/linux build_constants to
> make it work.
$(build)= is the correct syntax, sorry for the confusion.
Michal
next prev parent reply other threads:[~2016-01-25 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 11:33 Dependency issue through subdir's Kieran Bingham
2016-01-25 11:33 ` Kieran Bingham
2016-01-25 13:22 ` Michal Marek
2016-01-25 13:22 ` Michal Marek
2016-01-25 16:22 ` Kieran Bingham
2016-01-25 16:22 ` Kieran Bingham
2016-01-25 16:25 ` Michal Marek [this message]
2016-01-25 16:25 ` Michal Marek
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=56A64C69.7090000@suse.com \
--to=mmarek@suse.com \
--cc=jan.kiszka@siemens.com \
--cc=kieran@kbingham.co.uk \
--cc=lee.jones@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.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 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.