From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Cc: Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] MIPS: Constify static irq_domain_ops structs
Date: Tue, 22 Feb 2022 09:47:14 +0100 [thread overview]
Message-ID: <20220222084714.GB7123@alpha.franken.de> (raw)
In-Reply-To: <20220207211816.57860-1-rikard.falkeborn@gmail.com>
On Mon, Feb 07, 2022 at 10:18:13PM +0100, Rikard Falkeborn wrote:
> Constify a number of static irq_domain_ops structs that were never
> modified. This allows the compiler to put them in read-only memory.
>
> Rikard Falkeborn (3):
> MIPS: OCTEON: Constify static irq_domain_ops
> MIPS: ath25: Constify static irq_domain_ops
> MIPS: pci-ar2315: Constify static irq_domain_ops
>
> arch/mips/ath25/ar2315.c | 2 +-
> arch/mips/ath25/ar5312.c | 2 +-
> arch/mips/cavium-octeon/octeon-irq.c | 10 +++++-----
> arch/mips/pci/pci-ar2315.c | 2 +-
> 4 files changed, 8 insertions(+), 8 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-02-22 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 21:18 Rikard Falkeborn
2022-02-07 21:18 ` [PATCH 1/3] MIPS: OCTEON: Constify static irq_domain_ops Rikard Falkeborn
2022-02-07 21:18 ` [PATCH 2/3] MIPS: ath25: " Rikard Falkeborn
2022-02-07 21:18 ` [PATCH 3/3] MIPS: pci-ar2315: " Rikard Falkeborn
2022-02-22 8:47 ` Thomas Bogendoerfer [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=20220222084714.GB7123@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=rikard.falkeborn@gmail.com \
/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
all inboxes | Powered by JetHome®