From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: ysato@users.sourceforge.jp, dalias@libc.org
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: [PATCH 0/2] sh: use put_device() instead of kfree()
Date: Wed, 07 Mar 2018 11:15:12 +0000 [thread overview]
Message-ID: <cover.1520420267.git.arvind.yadav.cs@gmail.com> (raw)
Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.
Arvind Yadav (2):
[PATCH 1/2] sh: maple: use put_device() instead of kfree()
[PATCH 2/2] sh: superhyway: use put_device() if device_register fail
drivers/sh/maple/maple.c | 3 ++-
drivers/sh/superhyway/superhyway.c | 11 +++++++++--
2 files changed, 11 insertions(+), 3 deletions(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: ysato@users.sourceforge.jp, dalias@libc.org
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: [PATCH 0/2] sh: use put_device() instead of kfree()
Date: Wed, 7 Mar 2018 16:33:12 +0530 [thread overview]
Message-ID: <cover.1520420267.git.arvind.yadav.cs@gmail.com> (raw)
Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.
Arvind Yadav (2):
[PATCH 1/2] sh: maple: use put_device() instead of kfree()
[PATCH 2/2] sh: superhyway: use put_device() if device_register fail
drivers/sh/maple/maple.c | 3 ++-
drivers/sh/superhyway/superhyway.c | 11 +++++++++--
2 files changed, 11 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2018-03-07 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 11:03 Arvind Yadav [this message]
2018-03-07 11:15 ` [PATCH 0/2] sh: use put_device() instead of kfree() Arvind Yadav
2018-03-07 11:03 ` [PATCH 1/2] sh: maple: " Arvind Yadav
2018-03-07 11:15 ` Arvind Yadav
2018-03-07 11:03 ` [PATCH 2/2] sh: superhyway: use put_device() if device_register fail Arvind Yadav
2018-03-07 11:15 ` Arvind Yadav
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.1520420267.git.arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.