LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Blum <blum@kernel.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	Shrikanth Hegde <sshegde@linux.ibm.com>,
	Scott Wood <scottwood@freescale.com>,
	Stephen Chivers <schivers@mandarin.aust.csc.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Thorsten Blum <blum@kernel.org>
Subject: [PATCH 4/6] powerpc/embedded6xx: Use __func__ in mvme5100_pic_init()
Date: Mon,  2 Nov 2026 16:30:02 +0100	[thread overview]
Message-ID: <20261102152957.300019-12-blum@kernel.org> (raw)
In-Reply-To: <20261102152957.300019-8-blum@kernel.org>

Replace the hard-coded function names with __func__.

Signed-off-by: Thorsten Blum <blum@kernel.org>
---
 arch/powerpc/platforms/embedded6xx/mvme5100.c | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/arch/powerpc/platforms/embedded6xx/mvme5100.c b/arch/powerpc/platforms/embedded6xx/mvme5100.c
index b2979a2a1721..f22e10eb0c65 100644
--- a/arch/powerpc/platforms/embedded6xx/mvme5100.c
+++ b/arch/powerpc/platforms/embedded6xx/mvme5100.c
@@ -75,13 +75,13 @@ static void __init mvme5100_pic_init(void)
 
 	cp = of_find_compatible_node(NULL, NULL, "chrp,iic");
 	if (cp == NULL) {
-		pr_warn("mvme5100_pic_init: couldn't find i8259\n");
+		pr_warn("%s: couldn't find i8259\n", __func__);
 		return;
 	}
 
 	cirq = irq_of_parse_and_map(cp, 0);
 	if (!cirq) {
-		pr_warn("mvme5100_pic_init: no cascade interrupt?\n");
+		pr_warn("%s: no cascade interrupt?\n", __func__);
 		return;
 	}
 
@@ -96,8 +96,7 @@ static void __init mvme5100_pic_init(void)
 	}
 
 	if (intack)
-		pr_debug("mvme5100_pic_init: PCI 8259 intack at 0x%016lx\n",
-		   intack);
+		pr_debug("%s: PCI 8259 intack at 0x%016lx\n", __func__, intack);
 
 	i8259_init(cp, intack);
 	of_node_put(cp);


  parent reply	other threads:[~2026-11-02 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 15:29 [PATCH 0/6] powerpc: MVME5100 fixes and cleanups Thorsten Blum
2026-11-02 15:29 ` [PATCH 1/6] powerpc: dts: mvme5100: Drop #interrupt-cells from ISA node Thorsten Blum
2026-11-02 15:30 ` [PATCH 2/6] powerpc/embedded6xx: Validate bus-range length in mvme5100_add_bridge() Thorsten Blum
2026-11-02 15:30 ` [PATCH 3/6] powerpc/embedded6xx: Fix logged function name " Thorsten Blum
2026-11-02 15:30 ` Thorsten Blum [this message]
2026-11-02 15:30 ` [PATCH 5/6] powerpc/embedded6xx: Mark pci_membase as __initdata Thorsten Blum
2026-11-02 15:30 ` [PATCH 6/6] powerpc/embedded6xx: Drop redundant initializations Thorsten Blum

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=20261102152957.300019-12-blum@kernel.org \
    --to=blum@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=ritesh.list@gmail.com \
    --cc=robh@kernel.org \
    --cc=schivers@mandarin.aust.csc.com \
    --cc=scottwood@freescale.com \
    --cc=sshegde@linux.ibm.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