From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-actions@lists.infradead.org"
<linux-actions@lists.infradead.org>,
"linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-amlogic@lists.infradead.org"
<linux-amlogic@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@axis.com>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-rpi-kernel@lists.infradead.org"
<linux-rpi-kernel@lists.infradead.org>,
"chrome-platform@lists.linux.dev"
<chrome-platform@lists.linux.dev>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"kernel@dh-electronics.com" <kernel@dh-electronics.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-oxnas@groups.io" <linux-oxnas@groups.io>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-unisoc@lists.infradead.org"
<linux-unisoc@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>
Subject: Re: [RFC PATCH 1/1] ARM/arm64: categorize dts in arm dir and fix dependency in arm64
Date: Mon, 28 Mar 2022 10:28:58 +0200 [thread overview]
Message-ID: <20220328082858.GJ7371@axis.com> (raw)
In-Reply-To: <20220328000915.15041-2-ansuelsmth@gmail.com>
Hi Ansuel,
On Mon, Mar 28, 2022 at 02:09:15AM +0200, Ansuel Smith wrote:
> - Categorize every dts in arm directory in subdirectory
> - Fix Makefile to address for the arm subdirectory
> - Fix any arm64 dependency
> [...]
> arch/arm/boot/dts/axix/Makefile | 3 +
> .../boot/dts/{ => axix}/artpec6-devboard.dts | 0
> arch/arm/boot/dts/{ => axix}/artpec6.dtsi | 0
All ARTPEC platforms should be in a directory called "axis".
Otherwise LGTM.
Thanks!
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2022-03-28 8:30 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 0:09 [RFC PATCH 0/1] Categorize ARM dts directory Ansuel Smith
2022-03-28 0:09 ` [RFC PATCH 1/1] ARM/arm64: categorize dts in arm dir and fix dependency in arm64 Ansuel Smith
2022-03-28 7:57 ` [PATCH RFC " Geert Uytterhoeven
2022-03-28 8:28 ` Jesper Nilsson [this message]
2022-03-28 11:55 ` [RFC PATCH " Ansuel Smith
2022-03-28 9:09 ` [Linux-stm32] " Patrice CHOTARD
2022-03-28 9:20 ` Patrice CHOTARD
2022-03-28 11:59 ` Ansuel Smith
2022-03-28 12:11 ` Patrice CHOTARD
2022-03-28 10:47 ` Matthias Brugger
2022-03-28 11:54 ` Ansuel Smith
2022-03-29 13:03 ` Romain Perier
2022-03-28 8:55 ` [RFC PATCH 0/1] Categorize ARM dts directory Daniel Palmer
2022-03-29 7:53 ` Tony Lindgren
2022-03-29 8:32 ` Andrew Jeffery
2022-03-29 9:04 ` Geert Uytterhoeven
2022-03-29 9:54 ` Tony Lindgren
2022-03-29 10:06 ` Matthias Brugger
2022-03-29 8:50 ` Nicolas Ferre
2023-04-25 16:21 ` Robin Murphy
2023-05-02 19:01 ` Rob Herring
2022-03-28 13:21 ` Jonathan Neuschäfer
2022-03-28 13:27 ` Ansuel Smith
2022-03-28 13:35 ` Jonathan Neuschäfer
2022-03-28 13:50 ` H. Nikolaus Schaller
2022-03-29 0:23 ` Andrew Jeffery
2022-03-28 14:00 ` (EXT) " Alexander Stein
2022-03-29 9:19 ` Alexandre Belloni
2022-03-29 13:20 ` Krzysztof Kozlowski
2022-03-29 4:56 ` Ansuel Smith
2023-04-24 22:10 ` Rob Herring
2023-04-24 22:23 ` Ansuel Smith
2023-04-27 7:34 ` Matthias Brugger
2023-04-25 7:27 ` Geert Uytterhoeven
2023-04-25 15:57 ` Rob Herring
2023-04-27 7:37 ` Matthias Brugger
2023-04-27 7:46 ` Geert Uytterhoeven
2023-04-27 7:48 ` Tony Lindgren
2023-05-02 8:15 ` Arnd Bergmann
2023-05-02 19:40 ` Rob Herring
2023-05-02 20:02 ` Krzysztof Kozlowski
2023-05-03 1:19 ` Shawn Guo
2023-05-03 10:43 ` Arnd Bergmann
2023-05-02 21:18 ` Linus Walleij
2023-05-02 21:27 ` Rob Herring
2023-05-02 22:01 ` Christian Hewitt
2023-05-03 10:42 ` Neil Armstrong
2023-05-02 22:52 ` Dmitry Baryshkov
2023-05-03 1:17 ` Rob Herring
2023-05-03 10:38 ` Arnd Bergmann
2023-05-03 12:13 ` Dmitry Baryshkov
2023-05-03 12:18 ` Arnd Bergmann
2023-05-03 13:16 ` Rob Herring
2023-05-03 20:37 ` Arnd Bergmann
2023-05-03 20:39 ` Linus Walleij
2023-05-03 22:22 ` Rob Herring
2023-05-02 23:02 ` Florian Fainelli
2023-05-03 1:04 ` Rob Herring
2023-05-03 22:29 ` Florian Fainelli
2023-05-03 5:57 ` Tony Lindgren
2023-05-03 8:56 ` Geert Uytterhoeven
2023-05-03 11:02 ` Arnd Bergmann
2023-05-03 13:08 ` Rob Herring
2023-05-03 20:25 ` Linus Walleij
2023-05-04 7:09 ` [Linux-stm32] " Alexandre TORGUE
2023-05-03 12:01 ` Jesper Nilsson
2023-05-04 10:11 ` Russell King (Oracle)
2023-05-04 11:44 ` Arnd Bergmann
2023-05-09 22:54 ` Jonathan Neuschäfer
2023-06-08 20:33 ` Rob Herring
2023-04-25 8:00 ` Krzysztof Kozlowski
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=20220328082858.GJ7371@axis.com \
--to=jesper.nilsson@axis.com \
--cc=ansuelsmth@gmail.com \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-oxnas@groups.io \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-unisoc@lists.infradead.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).