From: Greg KH <gregkh@linuxfoundation.org>
To: Bo YU <tsu.yubo@gmail.com>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org, joe@perches.com,
yuzibode@126.com
Subject: Re: [PATCH v3 2/2] kobject: drop newline from msg string
Date: Fri, 7 Dec 2018 13:04:05 +0100 [thread overview]
Message-ID: <20181207120405.GC15336@kroah.com> (raw)
In-Reply-To: <f03d23a34df36d55274c5cce7d4081d9017668c1.1544175417.git.tsu.yubo@gmail.com>
On Fri, Dec 07, 2018 at 05:21:49AM -0500, Bo YU wrote:
> There is currently a missing terminating newline in non-switch case
> match, when msg == NULL.
>
> Signed-off-by: Bo YU <tsu.yubo@gmail.com>
> ---
> Changes in v3:
> Improve the commit log,requested by rafael.
>
> Changes in v2:
> According to Joe's suggestion,drop newline from msg
>
> lib/kobject_uevent.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
> index b7c088c902a2..1837765ebf01 100644
> --- a/lib/kobject_uevent.c
> +++ b/lib/kobject_uevent.c
> @@ -195,12 +195,12 @@ int kobject_synth_uevent(struct kobject *kobj, const char *buf, size_t count)
> enum kobject_action action;
> const char *action_args;
> struct kobj_uevent_env *env;
> - const char *msg = NULL, *devpath;
> + const char *msg = NULL;
Why did you move the devpath variable from here to lower down? That
really doesn't do anything :(
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-07 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 10:20 [PATCH v3 0/2] kobject: trival fix Bo YU
2018-12-07 10:21 ` [PATCH v3 1/2] kobject: use pr_warn to replace printk Bo YU
2018-12-07 10:21 ` [PATCH v3 2/2] kobject: drop newline from msg string Bo YU
2018-12-07 12:04 ` Greg KH [this message]
2018-12-07 14:43 ` 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=20181207120405.GC15336@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tsu.yubo@gmail.com \
--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