DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 3/7] platform-v8a: move platform menu files to platforms/
Date: Fri, 2 Jun 2023 18:44:36 +0200	[thread overview]
Message-ID: <8d3a9e71-3c0d-a8b5-90b3-3b16ae03effc@pengutronix.de> (raw)
In-Reply-To: <20230602145957.902307-4-m.olbrich@pengutronix.de>

On 02.06.23 16:59, Michael Olbrich wrote:
> Menu files that are only use for the platformconfig and not the
> ptxconfig belong in platforms/.

What functional change does this introduce?

> 
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> ---
>  configs/platform-v8a/{rules => platforms}/firmware-imx.in      | 0
>  configs/platform-v8a/{rules => platforms}/firmware-rockchip.in | 0
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  rename configs/platform-v8a/{rules => platforms}/firmware-imx.in (100%)
>  rename configs/platform-v8a/{rules => platforms}/firmware-rockchip.in (100%)
> 
> diff --git a/configs/platform-v8a/rules/firmware-imx.in b/configs/platform-v8a/platforms/firmware-imx.in
> similarity index 100%
> rename from configs/platform-v8a/rules/firmware-imx.in
> rename to configs/platform-v8a/platforms/firmware-imx.in
> diff --git a/configs/platform-v8a/rules/firmware-rockchip.in b/configs/platform-v8a/platforms/firmware-rockchip.in
> similarity index 100%
> rename from configs/platform-v8a/rules/firmware-rockchip.in
> rename to configs/platform-v8a/platforms/firmware-rockchip.in

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2023-06-02 16:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 14:59 [DistroKit] [PATCH 0/7] platform-v8a: cleanup firmware rules Michael Olbrich
2023-06-02 14:59 ` [DistroKit] [PATCH 1/7] platform-v8a: cleanup barebox firmware handling Michael Olbrich
2023-06-02 16:40   ` Ahmad Fatoum
2023-06-08  9:19     ` Michael Olbrich
2023-06-02 14:59 ` [DistroKit] [PATCH 2/7] firmware-imx: move to the correct section Michael Olbrich
2023-06-02 16:41   ` Ahmad Fatoum
2023-06-02 14:59 ` [DistroKit] [PATCH 3/7] platform-v8a: move platform menu files to platforms/ Michael Olbrich
2023-06-02 16:44   ` Ahmad Fatoum [this message]
2023-06-08  9:22     ` Michael Olbrich
2023-06-08  9:27       ` Ahmad Fatoum
2023-06-02 14:59 ` [DistroKit] [PATCH 4/7] platform-v8a: simplify dts search path Michael Olbrich
2023-06-02 16:44   ` Ahmad Fatoum
2023-06-02 14:59 ` [DistroKit] [PATCH 5/7] firmware-imx: use foreach and ptx/nl Michael Olbrich
2023-06-02 16:45   ` Ahmad Fatoum
2023-06-02 14:59 ` [DistroKit] [PATCH 6/7] firmware-imx: make sure menuconfig works correctly Michael Olbrich
2023-06-02 16:38   ` Ahmad Fatoum
2023-06-08  9:25     ` [DistroKit] [PATCH v2] " Michael Olbrich
2023-06-08  9:27       ` Ahmad Fatoum
2023-06-02 14:59 ` [DistroKit] [PATCH 7/7] firmware-rockchip: " Michael Olbrich
2023-06-20 13:26 ` [DistroKit] [PATCH 0/7] platform-v8a: cleanup firmware rules Robert Schwebel

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=8d3a9e71-3c0d-a8b5-90b3-3b16ae03effc@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    /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