From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-kbuild@vger.kernel.org, maximilian attems <max@stro.at>
Subject: Re: [PATCHv2 1/1] deb-pkg: Add device tree blobs to the package
Date: Thu, 22 Jan 2015 16:58:13 +0100 [thread overview]
Message-ID: <87d266iz8q.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <54C11776.2070808@suse.cz> (Michal Marek's message of "Thu, 22 Jan 2015 16:29:58 +0100")
Michal Marek <mmarek@suse.cz> writes:
> On 2015-01-22 15:19, Ben Hutchings wrote:
>> On Thu, 2015-01-22 at 14:40 +0100, Michal Marek wrote:
>>> On 2015-01-20 17:04, Ben Hutchings wrote:
>>>> On Tue, 2015-01-20 at 00:13 +0100, Arnaud Patard wrote:
>>>>> Ben Hutchings <ben@decadent.org.uk> writes:
>>>>>> Only arm and arm64 support that target. You should maybe run something
>>>>>> like 'make -n dtbs_install >/dev/null 2>&1' first to check that the
>>>>>> target is defined.
>>>>>
>>>>> There's a 'set -e' on top of the script so using make -n will likely
>>>>> result in the script failing, which wouldn't be so nice imho.
>>>> [...]
>>>>
>>>> That's why you use it with the if statement:
>>>>
>>>> # Only some architectures with OF support have this target
>>>> if make -n dtbs_install >/dev/null 2>&1; then
>>>
>>> The problem is that kbuild does not support make -n and some of the
>>> commands are always executed. So the command will silently build the
>>> blobs and just not install them.
>>
>> If the dtbs_install target is defined, they should already have been
>> built at this point. If the target is not defined, why would it do
>> anything?
>
> The point is that make -n does not work with kbuild. It might work for
> this specific case, but there is no guarantee that it will continue to
> do so.
>
Ok, so a patch with make -n will be refused, right ?
>
>>> if grep -q dtbs_install "arch/$SRCARCH/Makefile"; then
>>> ...
>>>
>>> and hope that there won't be any comment causing a false positive.
>>> Another option is to grep 'make help' output.
>>
>> Ugh.
>
> I know that both options are ugly :).
Let's go to your first options then. I feel not really motivated by
parsing 'make help' output.
Arnaud
next prev parent reply other threads:[~2015-01-22 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 12:32 [PATCHv2 0/1] deb-pkg: Add device tree blobs to the package Arnaud Patard
2015-01-14 12:32 ` [PATCHv2 1/1] " Arnaud Patard
2015-01-14 12:51 ` Ben Hutchings
2015-01-19 23:13 ` Arnaud Patard
2015-01-20 16:04 ` Ben Hutchings
2015-01-22 10:24 ` Fathi Boudra
2015-01-22 13:15 ` Ben Hutchings
2015-01-22 13:40 ` Michal Marek
2015-01-22 14:19 ` Ben Hutchings
2015-01-22 15:29 ` Michal Marek
2015-01-22 15:58 ` Arnaud Patard [this message]
2015-01-23 9:55 ` 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=87d266iz8q.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--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