public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>
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: Fri, 23 Jan 2015 10:55:20 +0100	[thread overview]
Message-ID: <54C21A88.70505@suse.cz> (raw)
In-Reply-To: <87d266iz8q.fsf@lebrac.rtp-net.org>

On 2015-01-22 16:58, Arnaud Patard (Rtp) wrote:
> 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 ?

I'm not trying to veto such patch, I just wanted to point out that make
-n is not the best idea to do with kbuild.


> Let's go to your first options then. I feel not really motivated by
> parsing 'make help' output.

Whatever. You can also have a static list of archs supporting
dtbs_install, like we (still) have in scripts/headers.sh. It would be
guaranteed to works as designed, but obviously not future-proof.

Michal

      reply	other threads:[~2015-01-23  9:55 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
2015-01-23  9:55                 ` Michal Marek [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=54C21A88.70505@suse.cz \
    --to=mmarek@suse.cz \
    --cc=arnaud.patard@rtp-net.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=max@stro.at \
    /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