linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Balamuruhan S <bala24@linux.ibm.com>
Subject: [PATCH 0/3] powerpc: Use proper printk format specifiers
Date: Thu, 23 Apr 2020 20:47:34 +0530	[thread overview]
Message-ID: <cover.1587652966.git.naveen.n.rao@linux.vnet.ibm.com> (raw)

This series changes printk format specifiers from bare %p to %px/%pK in 
ftrace, kprobes and hw bkpts code. In addition, use of %lx is also 
changed over to conform to the recommended practice.

This series applies on top of the below patch series:
https://lore.kernel.org/r/cover.1587654213.git.naveen.n.rao@linux.vnet.ibm.com

- Naveen

Balamuruhan S (1):
  powerpc/kprobes: Use appropriate format specifier for printing kernel
    address

Naveen N. Rao (2):
  powerpc/ftrace: Use appropriate format specifier for printing kernel
    addresses
  powerpc/hw_bkpt: Update printk format specifiers for kernel addresses

 arch/powerpc/kernel/hw_breakpoint.c |  5 +-
 arch/powerpc/kernel/optprobes.c     |  2 +-
 arch/powerpc/kernel/trace/ftrace.c  | 74 ++++++++++++++++-------------
 3 files changed, 45 insertions(+), 36 deletions(-)


base-commit: 8299da600ad05b8aa0f15ec0f5f03bd40e37d6f0
-- 2.25.1


             reply	other threads:[~2020-04-23 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 15:17 Naveen N. Rao [this message]
2020-04-23 15:17 ` [PATCH 1/3] powerpc/kprobes: Use appropriate format specifier for printing kernel address Naveen N. Rao
2022-03-09 18:28   ` Christophe Leroy
2020-04-23 15:17 ` [PATCH 2/3] powerpc/ftrace: Use appropriate format specifier for printing kernel addresses Naveen N. Rao
2020-04-23 15:17 ` [PATCH 3/3] powerpc/hw_bkpt: Update printk format specifiers for " Naveen N. Rao

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=cover.1587652966.git.naveen.n.rao@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=bala24@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ravi.bangoria@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;
as well as URLs for NNTP newsgroup(s).