From: Marc Zyngier <maz@kernel.org>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Matthew Leaman <matthew@a-eon.biz>,
Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>
Subject: Re: [PATCH] of/irq: Don't ignore interrupt-controller when interrupt-map failed
Date: Fri, 12 Nov 2021 16:01:37 +0000 [thread overview]
Message-ID: <87ee7l8ise.wl-maz@kernel.org> (raw)
In-Reply-To: <aae33774-a09b-9585-abc7-57cfee5c84af@xenosoft.de>
On Fri, 12 Nov 2021 15:43:12 +0000,
Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>
> Could you please merge it asap for the RC1? Then we can compile the
> RC1 without these patches.
I don't think there is any rush. Plenty of things are broken at this
stage, and that's completely expected after merging a few thousand
patches. It is not like we are at -rc7 with a critical issue to
address right before release.
The problem is understood, the fix identified, and we have a patch
under review. This really is as good as it gets.
> Thanks to all for your help and sorry for bother you with all these
> mails. I do this work alongside my main job and actually I don't have
> time for bisecting.
And we're grateful for your help in identifying the problem.
"Don't Panic!".
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-11-12 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 14:36 [PATCH] of/irq: Don't ignore interrupt-controller when interrupt-map failed Marc Zyngier
2021-11-12 14:57 ` Rob Herring
2021-11-12 15:26 ` Marc Zyngier
2021-11-12 15:04 ` Bjorn Helgaas
2021-11-12 15:28 ` Marc Zyngier
2021-11-12 15:55 ` Rob Herring
2021-11-12 15:43 ` Christian Zigotzky
2021-11-12 16:01 ` Marc Zyngier [this message]
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=87ee7l8ise.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bhelgaas@google.com \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madskateman@gmail.com \
--cc=matthew@a-eon.biz \
--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).