public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: Remove example file on dt-extract-example error
Date: Mon, 16 May 2022 20:12:14 -0500	[thread overview]
Message-ID: <20220517011214.GA3716531-robh@kernel.org> (raw)
In-Reply-To: <CAK7LNAQYL7rkqsWfNSdS53_sf-SLqpuVeoSmZuGqRNNtScT6Hw@mail.gmail.com>

On Wed, May 11, 2022 at 09:27:00AM +0900, Masahiro Yamada wrote:
> On Wed, May 11, 2022 at 7:13 AM Rob Herring <robh@kernel.org> wrote:
> >
> > As 'dt-extract-example' writes the example dts files to stdout, a file
> > is always created even on an error such as Ctrl-C. The resulting empty
> > file(s) then cause unexpected errors on subsequent builds. Fix this by
> > removing the output file on any error.
> >
> 
> 
> Did you really set it?

Set what?

I'm sure I've gotten empty files which then throw errors on the next 
run.

> The target deletion on interrupt is automatic
> since the following commit:
> 
> 
> 
> commit 9c2af1c7377a8a6ef86e5cabf80978f3dbbb25c0
> Author: Masahiro Yamada <yamada.masahiro@socionext.com>
> Date:   Fri Jul 20 16:46:33 2018 +0900
> 
>     kbuild: add .DELETE_ON_ERROR special target

You're saying I shouldn't need this change? For some reason I do...

Rob

  reply	other threads:[~2022-05-17  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 22:13 [PATCH] dt-bindings: Remove example file on dt-extract-example error Rob Herring
2022-05-11  0:27 ` Masahiro Yamada
2022-05-17  1:12   ` Rob Herring [this message]
2022-05-17  3:02     ` Masahiro Yamada
2022-05-17 13:38       ` Rob Herring

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=20220517011214.GA3716531-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox