From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: apatel@ventanamicro.com, Rob Herring <robh@kernel.org>,
Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
DTML <devicetree@vger.kernel.org>, Marc Zyngier <maz@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
Matthew Leaman <matthew@a-eon.biz>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29
Date: Fri, 5 Jul 2024 15:45:52 -0500 [thread overview]
Message-ID: <20240705204552.GD19790@gate.crashing.org> (raw)
In-Reply-To: <87o77ciqj8.fsf@mail.lhotse>
On Fri, Jul 05, 2024 at 11:19:39AM +1000, Michael Ellerman wrote:
> + prom_printf("nemo: deleting interrupt-map properties\n");
> + rc = call_prom("interpret", 1, 1,
> + " s\" /pxp@0,e0000000\" find-device"
> + " s\" interrupt-map\" delete-property"
> + " s\" interrupt-map-mask\" delete-property"
> + " device-end");
> + prom_printf("nemo: interpret returned %d\n", rc);
It's very fragile no matter what.
If some scriupt does something bad, just add something better for it?
You can replace anything by just adding something with the same name!
Segher
next prev parent reply other threads:[~2024-07-05 20:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 10:21 [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29 Christian Zigotzky
2024-07-02 15:19 ` Marc Zyngier
2024-07-02 17:55 ` Christian Zigotzky
2024-07-02 19:49 ` Marc Zyngier
2024-07-03 3:11 ` Christian Zigotzky
2024-07-03 6:40 ` Marc Zyngier
2024-07-03 10:26 ` Christian Zigotzky
2024-07-03 10:41 ` Marc Zyngier
2024-07-03 16:23 ` Christian Zigotzky
2024-07-02 16:54 ` Marc Zyngier
2024-07-02 20:48 ` Rob Herring
2024-07-02 21:42 ` Marc Zyngier
2024-07-03 11:30 ` Michael Ellerman
2024-07-03 12:09 ` Marc Zyngier
2024-07-03 3:27 ` Christian Zigotzky
2024-07-03 6:41 ` Marc Zyngier
2024-07-04 4:10 ` Christian Zigotzky
2024-07-04 8:28 ` Marc Zyngier
2024-07-04 18:54 ` Christian Zigotzky
2024-07-05 7:05 ` Christian Zigotzky
2024-07-05 8:05 ` Christian Zigotzky
2024-07-05 13:01 ` Marc Zyngier
2024-07-05 13:30 ` Trevor Dickinson
2024-07-09 3:46 ` Damien Stewart
2024-07-09 12:48 ` Michael Ellerman
2024-07-04 11:53 ` Michael Ellerman
2024-07-04 18:27 ` Christian Zigotzky
2024-07-04 18:59 ` Christian Zigotzky
2024-07-05 1:19 ` Michael Ellerman
2024-07-05 20:45 ` Segher Boessenkool [this message]
2024-07-06 3:51 ` Christian Zigotzky
2024-07-06 4:15 ` Christian Zigotzky
2024-07-06 15:54 ` Christian Zigotzky
2024-07-10 3:53 ` Christian Zigotzky
2024-07-10 15:05 ` Rob Herring
2024-07-10 15:53 ` Christian Zigotzky
2024-07-06 4:08 ` Christian Zigotzky
2024-07-05 6:59 ` Christian Zigotzky
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=20240705204552.GD19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=apatel@ventanamicro.com \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=devicetree@vger.kernel.org \
--cc=info@xenosoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=matthew@a-eon.biz \
--cc=maz@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=robh@kernel.org \
--cc=rtd2@xtra.co.nz \
/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).