mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: YU Bo <tsu.yubo@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Joe Perches <joe@perches.com>,
	yuzibode@126.com
Subject: Re: [PATCH V5 2/2] kobject: drop newline from msg string
Date: Wed, 9 Jan 2019 04:30:16 -0500	[thread overview]
Message-ID: <20190109093014.cjheviy67szigzfg@yubo-2> (raw)
In-Reply-To: <CAJZ5v0guQizE2mi3qv=0CVz9FYf6Kzv222Ff0RX1NyGuKAiucA@mail.gmail.com>

On Wed, Jan 09, 2019 at 10:21:37AM +0100, Rafael J. Wysocki wrote:
>On Wed, Jan 9, 2019 at 10:17 AM Bo YU <tsu.yubo@gmail.com> 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>
>
>I have given you an R-by for this one already, so why haven't you added it here?
Oh, i got it.This is the first time i encountered the circumstances.
>
>Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Thank you :)
>
>> ---
>> Changes in V4:
>> Recovery originly declaration, requested by Greg.
>>
>> Change in V3:
>> Improve the commit log, requested by Rafael.
>>
>> Changes in V2:
>> Drop newline from msg according to Joe's suggestion.
>> ---
>>  lib/kobject_uevent.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
>> index c87a96c4800e..f05802687ba4 100644
>> --- a/lib/kobject_uevent.c
>> +++ b/lib/kobject_uevent.c
>> @@ -200,7 +200,7 @@ int kobject_synth_uevent(struct kobject *kobj, const char *buf, size_t count)
>>
>>         r = kobject_action_type(buf, count, &action, &action_args);
>>         if (r) {
>> -               msg = "unknown uevent action string\n";
>> +               msg = "unknown uevent action string";
>>                 goto out;
>>         }
>>
>> @@ -212,7 +212,7 @@ int kobject_synth_uevent(struct kobject *kobj, const char *buf, size_t count)
>>         r = kobject_action_args(action_args,
>>                                 count - (action_args - buf), &env);
>>         if (r == -EINVAL) {
>> -               msg = "incorrect uevent action arguments\n";
>> +               msg = "incorrect uevent action arguments";
>>                 goto out;
>>         }
>>
>> @@ -224,7 +224,7 @@ int kobject_synth_uevent(struct kobject *kobj, const char *buf, size_t count)
>>  out:
>>         if (r) {
>>                 devpath = kobject_get_path(kobj, GFP_KERNEL);
>> -               pr_warn("synth uevent: %s: %s",
>> +               pr_warn("synth uevent: %s: %s\n",
>>                        devpath ?: "unknown device",
>>                        msg ?: "failed to send uevent");
>>                 kfree(devpath);
>> --
>> 2.11.0
>>

      reply	other threads:[~2019-01-09  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  9:16 [PATCH V5 0/2] kobject: fix code style and drop newline Bo YU
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 [this message]

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=20190109093014.cjheviy67szigzfg@yubo-2 \
    --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

all inboxes | Powered by JetHome®