From: Greg KH <gregkh@linuxfoundation.org>
To: Dong Hao <haodong@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplify the kobject_init function.
Date: Tue, 17 Jul 2012 09:40:24 -0700 [thread overview]
Message-ID: <20120717164024.GA7225@kroah.com> (raw)
In-Reply-To: <1342073375-27181-1-git-send-email-haodong@linux.vnet.ibm.com>
On Thu, Jul 12, 2012 at 02:09:35PM +0800, Dong Hao wrote:
> The printk() function at the end of function kobject_init() already had '\n',
> so remove it.
>
> While the kobject has been initialized, assign error string and
> jump to error case directly.
>
> Signed-off-by: Dong Hao<haodong@linux.vnet.ibm.com>
> ---
> lib/kobject.c | 9 ++++-----
> 1 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/lib/kobject.c b/lib/kobject.c
> index 05de4dc..7b8a09c 100644
> --- a/lib/kobject.c
> +++ b/lib/kobject.c
> @@ -278,14 +278,13 @@ void kobject_init(struct kobject *kobj, struct kobj_type *ktype)
> goto error;
> }
> if (!ktype) {
> - err_str = "must have a ktype to be initialized properly!\n";
> + err_str = "must have a ktype to be initialized properly!";
> goto error;
> }
> if (kobj->state_initialized) {
> - /* do not error out as sometimes we can recover */
> - printk(KERN_ERR "kobject (%p): tried to init an initialized "
> - "object, something is seriously wrong.\n", kobj);
> - dump_stack();
> + err_str = "tried to init an initialized "
> + "object, something is seriously wrong.";
> + goto error;
You were already told why this patch is incorrect, why are you resending
it two more times? That's a bit annoying and rude, don't you think?
Sorry, I can't take this, please read the code you are modifying.
greg k-h
next parent reply other threads:[~2012-07-17 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1342073375-27181-1-git-send-email-haodong@linux.vnet.ibm.com>
2012-07-17 16:40 ` Greg KH [this message]
2012-07-18 4:46 ` [PATCH] Simplify the kobject_init function don
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=20120717164024.GA7225@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haodong@linux.vnet.ibm.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.