From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: rientjes@google.com, liuj97@gmail.com, minchan.kim@gmail.com,
akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com,
isimatu.yasuaki@jp.fujitsu.com, wency@cn.fujitsu.com
Subject: [PATCH v2 0/2] Suppress "Device <device name> does not have a release() function" warning
Date: Thu, 11 Oct 2012 14:19:13 +0900 [thread overview]
Message-ID: <507656D1.5020703@jp.fujitsu.com> (raw)
This patch-set is patches to which [1] and [2] are updated
[1] memory-hotplug: add memory_block_release
[2] memory-hotplug: add node_device_release
from following patch-set.
https://lkml.org/lkml/2012/9/27/39
So the patch-set version is v2.
v1 -> v2
[PATCH 1/2]
- change subject to Suppress "Device memoryX does not have a release()
function" warning.
- Add detail information into description
- change function name from release_memory_block() to memory_block_release(),
because other device release() function is named to <device_name>_release()
[PATCH 2/2]
- change subject to Suppress "Device nodeX does not have a release() function"
warning.
- Add detail information into description
- Remove memset() to initialize a node struct from node_device_release()
- Add memset() to initialize a node struct into register_node()
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Cc: <rientjes@google.com>, <liuj97@gmail.com>,
<minchan.kim@gmail.com>, <akpm@linux-foundation.org>,
<kosaki.motohiro@jp.fujitsu.com>,
<isimatu.yasuaki@jp.fujitsu.com>, <wency@cn.fujitsu.com>
Subject: [PATCH v2 0/2] Suppress "Device <device name> does not have a release() function" warning
Date: Thu, 11 Oct 2012 14:19:13 +0900 [thread overview]
Message-ID: <507656D1.5020703@jp.fujitsu.com> (raw)
This patch-set is patches to which [1] and [2] are updated
[1] memory-hotplug: add memory_block_release
[2] memory-hotplug: add node_device_release
from following patch-set.
https://lkml.org/lkml/2012/9/27/39
So the patch-set version is v2.
v1 -> v2
[PATCH 1/2]
- change subject to Suppress "Device memoryX does not have a release()
function" warning.
- Add detail information into description
- change function name from release_memory_block() to memory_block_release(),
because other device release() function is named to <device_name>_release()
[PATCH 2/2]
- change subject to Suppress "Device nodeX does not have a release() function"
warning.
- Add detail information into description
- Remove memset() to initialize a node struct from node_device_release()
- Add memset() to initialize a node struct into register_node()
next reply other threads:[~2012-10-11 5:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 5:19 Yasuaki Ishimatsu [this message]
2012-10-11 5:19 ` [PATCH v2 0/2] Suppress "Device <device name> does not have a release() function" warning Yasuaki Ishimatsu
2012-10-11 5:22 ` [PATCH 1/2]suppress "Device memoryX " Yasuaki Ishimatsu
2012-10-11 5:22 ` Yasuaki Ishimatsu
2012-10-11 20:23 ` David Rientjes
2012-10-11 20:23 ` David Rientjes
2012-10-11 22:30 ` KOSAKI Motohiro
2012-10-11 22:30 ` KOSAKI Motohiro
2012-10-11 5:26 ` [PATCH 2/2]suppress "Device nodeX " Yasuaki Ishimatsu
2012-10-11 5:26 ` Yasuaki Ishimatsu
2012-10-11 20:31 ` David Rientjes
2012-10-11 20:31 ` David Rientjes
2012-10-12 0:13 ` Yasuaki Ishimatsu
2012-10-12 0:13 ` Yasuaki Ishimatsu
2012-10-11 22:33 ` KOSAKI Motohiro
2012-10-11 22:33 ` KOSAKI Motohiro
2012-10-17 6:24 ` Wen Congyang
2012-10-17 6:24 ` Wen Congyang
2012-10-17 8:50 ` KOSAKI Motohiro
2012-10-17 8:50 ` KOSAKI Motohiro
2012-10-19 5:42 ` Wen Congyang
2012-10-19 5:42 ` Wen Congyang
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=507656D1.5020703@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
--cc=wency@cn.fujitsu.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 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.