From: Marc Zyngier <maz@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Jonas Gorski <jonas.gorski@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 0/2] irqchip: add support for BCM6345 interrupt controller
Date: Sat, 27 Feb 2021 10:07:47 +0000 [thread overview]
Message-ID: <87a6rpsu18.wl-maz@kernel.org> (raw)
In-Reply-To: <1C119275-4A6D-4E72-BBAA-D9DDF25485C8@gmail.com>
Alvaro,
On Sat, 27 Feb 2021 08:49:25 +0000,
Álvaro Fernández Rojas <noltari@gmail.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.
next parent reply other threads:[~2021-02-27 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHp75VfmZ7ULAHOmXdxw7F1gtkaU7JJNWv+35Nx96f-evt8=bA@mail.gmail.com>
[not found] ` <1C119275-4A6D-4E72-BBAA-D9DDF25485C8@gmail.com>
2021-02-27 10:07 ` Marc Zyngier [this message]
2021-02-23 18:08 [PATCH 0/2] irqchip: add support for BCM6345 interrupt controller Álvaro Fernández Rojas
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=87a6rpsu18.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).