All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: linux-kbuild@vger.kernel.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Pantelis Antoniou" <pantelis.antoniou@konsulko.com>,
	devicetree@vger.kernel.org,
	"Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"Matthias Kaehlcke" <mka@chromium.org>,
	"Behan Webster" <behanw@converseincode.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Tobias Klauser" <tklauser@distanz.ch>,
	"Ley Foon Tan" <ley.foon.tan@intel.com>,
	"Vinícius Tinti" <viniciustinti@gmail.com>,
	"Josh Poimboeuf" <jpoimboe@redhat.com>
Subject: [PATCH 0/3] .gitignore / kbuild: of: ignore and clean *.dtb and *.dtb.S globally
Date: Tue, 31 Oct 2017 00:33:44 +0900	[thread overview]
Message-ID: <1509377627-11362-1-git-send-email-yamada.masahiro@socionext.com> (raw)


Recently, overlay test data were added to of/unittest-data,
but I notice they are not ignored or cleaned.  Actually, we
often forget .gitignore / clean-files at the first commit.

We have DT things in various places in the kernel tree,
so I think it is OK to move them to the top-level.

Is this OK from the DT point of view?



Masahiro Yamada (3):
  .gitignore: sort normal pattern rules alphabetically
  .gitignore: move *.dtb and *.dtb.S patterns to the top-level
    .gitignore
  kbuild: clean up *.dtb and *.dtb.S patterns from top-level Makefile

 .gitignore                          | 44 +++++++++++++++++++------------------
 Makefile                            |  2 +-
 arch/arc/boot/.gitignore            |  1 -
 arch/arm/boot/.gitignore            |  1 -
 arch/arm64/boot/dts/.gitignore      |  1 -
 arch/metag/boot/.gitignore          |  1 -
 arch/microblaze/boot/.gitignore     |  1 -
 arch/mips/boot/.gitignore           |  1 -
 arch/nios2/boot/.gitignore          |  1 -
 arch/powerpc/boot/.gitignore        |  1 -
 arch/xtensa/boot/.gitignore         |  1 -
 drivers/of/unittest-data/.gitignore |  2 --
 12 files changed, 24 insertions(+), 33 deletions(-)
 delete mode 100644 arch/arm64/boot/dts/.gitignore
 delete mode 100644 drivers/of/unittest-data/.gitignore

-- 
2.7.4


             reply	other threads:[~2017-10-30 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 15:33 Masahiro Yamada [this message]
     [not found] ` <1509377627-11362-1-git-send-email-yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
2017-10-30 15:33   ` [PATCH 1/3] .gitignore: sort normal pattern rules alphabetically Masahiro Yamada
2017-10-30 15:33     ` Masahiro Yamada
2017-10-30 15:33 ` [PATCH 2/3] .gitignore: move *.dtb and *.dtb.S patterns to the top-level .gitignore Masahiro Yamada
2017-10-30 15:33 ` [PATCH 3/3] kbuild: clean up *.dtb and *.dtb.S patterns from top-level Makefile Masahiro Yamada
2017-10-30 15:53   ` Rob Herring
2017-10-30 16:32     ` Masahiro Yamada
2017-11-01 21:45       ` 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=1509377627-11362-1-git-send-email-yamada.masahiro@socionext.com \
    --to=yamada.masahiro@socionext.com \
    --cc=behanw@converseincode.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=ley.foon.tan@intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mka@chromium.org \
    --cc=mpe@ellerman.id.au \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.org \
    --cc=tklauser@distanz.ch \
    --cc=viniciustinti@gmail.com \
    /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.