[<prev] [next>] [day] [month] [year] [list]
Message-ID: <87a6rpsu18.wl-maz@kernel.org>
Date: Sat, 27 Feb 2021 10:07:47 +0000
From: Marc Zyngier <maz@...nel.org>
To: Álvaro Fernández Rojas <noltari@...il.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Jonas Gorski <jonas.gorski@...il.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com, linux-mips@...r.kernel.org
Subject: Re: [PATCH 0/2] irqchip: add support for BCM6345 interrupt controller
Alvaro,
On Sat, 27 Feb 2021 08:49:25 +0000,
Álvaro Fernández Rojas <noltari@...il.com> wrote:
>
> Hi Andy,
>
> That wasn’t top-posting,
If that isn't top-posting, I wonder what is. With HTML on top, to make
sure it breaks every established rule.
> I was just asking why it was changed to Not Applicable instead of
> leaving it as New until the merge window closes...
I have no idea why, and I don't really care. I don't use patchwork for
anything I maintain, and the sole reference is the state of my Inbox.
> I have the feeling that if the patch is changed to Not Applicable
> it’s going to be forgotten after the merge window closes...
If you haven't received any feedback on your patches within a few
*weeks*, feel free to point them again to the relevant people (me, at
least).
Documentation/process/submitting-patches.rst describes the process I
(and most other kernel people) use. Feel free to refer to it.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists