From: Chuhong Yuan <hslester96@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
kgdb-bugreport@lists.sourceforge.net, Pavel Machek <pavel@ucw.cz>,
Christoph Hellwig <hch@lst.de>,
Daniel Thompson <daniel.thompson@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Jason Wessel <jason.wessel@windriver.com>,
Len Brown <len.brown@intel.com>,
linux-pm@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
Chuhong Yuan <hslester96@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
cgroups@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
iommu@lists.linux-foundation.org, Li Zefan <lizefan@huawei.com>,
Jessica Yu <jeyu@kernel.org>, Tejun Heo <tj@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH 00/12] Replace strncmp with str_has_prefix
Date: Mon, 29 Jul 2019 23:13:23 +0800 [thread overview]
Message-ID: <20190729151323.9226-1-hslester96@gmail.com> (raw)
The commit 72921427d46b
("string.h: Add str_has_prefix() helper function")
introduced str_has_prefix() to substitute error-prone
strncmp(str, const, len).
The commit b6b2735514bc
("tracing: Use str_has_prefix() instead of using fixed sizes")
has fixed some codes.
These patches use str_has_prefix to replace
such pattern of strncmp usages.
Chuhong Yuan (12):
rdmacg: Replace strncmp with str_has_prefix
kdb: Replace strncmp with str_has_prefix
dma-debug: Replace strncmp with str_has_prefix
gcov: Replace strncmp with str_has_prefix
genirq/debugfs: Replace strncmp with str_has_prefix
module: Replace strncmp with str_has_prefix
power: Replace strncmp with str_has_prefix
printk: Replace strncmp with str_has_prefix
reboot: Replace strncmp with str_has_prefix
sched: Replace strncmp with str_has_prefix
userns: Replace strncmp with str_has_prefix
watchdog: Replace strncmp with str_has_prefix
kernel/cgroup/rdma.c | 2 +-
kernel/debug/kdb/kdb_main.c | 2 +-
kernel/dma/debug.c | 2 +-
kernel/gcov/fs.c | 2 +-
kernel/irq/debugfs.c | 2 +-
kernel/module.c | 2 +-
kernel/power/hibernate.c | 8 ++++----
kernel/power/main.c | 2 +-
kernel/printk/braille.c | 4 ++--
kernel/printk/printk.c | 6 +++---
kernel/reboot.c | 2 +-
kernel/sched/debug.c | 2 +-
kernel/sched/isolation.c | 4 ++--
kernel/user_namespace.c | 4 ++--
kernel/watchdog.c | 8 ++++----
15 files changed, 26 insertions(+), 26 deletions(-)
--
2.20.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
reply other threads:[~2019-07-29 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190729151323.9226-1-hslester96@gmail.com \
--to=hslester96@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=jeyu@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=oberpar@linux.ibm.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rjw@rjwysocki.net \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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