From: Bo YU <tsu.yubo@gmail.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org
Cc: Bo YU <tsu.yubo@gmail.com>,
linux-kernel@vger.kernel.org, joe@perches.com, yuzibode@126.com
Subject: [PATCH V5 0/2] kobject: fix code style and drop newline
Date: Wed, 9 Jan 2019 04:16:38 -0500 [thread overview]
Message-ID: <cover.1547024167.git.tsu.yubo@gmail.com> (raw)
There are some mirror changes in kobject_uevent.c.
Btw, this is v5 for the patchset.2/2 was fixed by v1-v4,but 1/2 was marked
V2 :(.
Bo YU (2):
kobject: to repalce printk with pr_* style
kobject: drop newline from msg string
lib/kobject_uevent.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
--
2.11.0
next reply other threads:[~2019-01-09 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 9:16 Bo YU [this message]
2019-01-09 9:17 ` [PATCH V5 1/2] kobject: to repalce printk with pr_* style Bo YU
2019-01-09 9:20 ` Rafael J. Wysocki
2019-01-09 9:17 ` [PATCH V5 2/2] kobject: drop newline from msg string Bo YU
2019-01-09 9:21 ` Rafael J. Wysocki
2019-01-09 9:30 ` YU Bo
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.1547024167.git.tsu.yubo@gmail.com \
--to=tsu.yubo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yuzibode@126.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).