Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Avram Lubkin <avram@rockhopper.net>
Cc: robh@kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	conor+dt@kernel.org, liviu.dudau@arm.com,
	krzysztof.kozlowski+dt@linaro.org, lpieralisi@kernel.org,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: Bug introduced in 724ba67 (ARM: dts: Move .dts files to vendor sub-directories)
Date: Thu, 6 Jul 2023 09:45:11 +0100	[thread overview]
Message-ID: <20230706084511.gp4iuvekkw7lwhdl@bogus> (raw)
In-Reply-To: <CAHqEdrPD_EX=V0RnvvycN1MyXs0e+jkCcQ-nfHwOmyZR2LecfA@mail.gmail.com>

On Wed, Jul 05, 2023 at 10:16:19AM -0400, Avram Lubkin wrote:
> Resending in plain text mode
> 
> SImple bug introduced in 724ba6751532055db75992fc6ae21c3e322e94a7.
> 
> The file
>   arch/arm/boot/dts/vexpress-v2m-rs1.dtsi
> was moved to
>   arch/arm/boot/dts/arm/vexpress-v2m-rs1.dtsi
> 
> However,
>   arch/arm64/boot/dts/arm/vexpress-v2m-rs1.dtsi
> is a symlink and still points to the old location
>   ../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi
>

It doesn't break any compilation as it is taken care. I will submit a patch
to remove the symlink soon. Thanks for the report.


-- 
Regards,
Sudeep

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-07-06  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHqEdrPuH4ayMiiq5FixaNjM=r44VJOw-v3iQ0mek55FTUWpsw@mail.gmail.com>
2023-07-05 14:16 ` Bug introduced in 724ba67 (ARM: dts: Move .dts files to vendor sub-directories) Avram Lubkin
2023-07-06  8:45   ` Sudeep Holla [this message]
2023-07-13 17:38     ` Avram Lubkin
2023-07-14 11:08       ` Sudeep Holla

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=20230706084511.gp4iuvekkw7lwhdl@bogus \
    --to=sudeep.holla@arm.com \
    --cc=avram@rockhopper.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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