mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-12-29 01:05:29 +00:00
docs: filesystems: fix renamed references
Some filesystem references got broken by a previous patch series I submitted. Address those. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Acked-by: David Sterba <dsterba@suse.com> # fs/affs/Kconfig Link: https://lore.kernel.org/r/57318c53008dbda7f6f4a5a9e5787f4d37e8565a.1586881715.git.mchehab+huawei@kernel.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
3ecad8c2c1
commit
0c1bc6b845
@ -54,7 +54,7 @@ Date: October 2002
|
||||
Contact: Linux Memory Management list <linux-mm@kvack.org>
|
||||
Description:
|
||||
Provides information about the node's distribution and memory
|
||||
utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.txt
|
||||
utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst
|
||||
|
||||
What: /sys/devices/system/node/nodeX/numastat
|
||||
Date: October 2002
|
||||
|
@ -11,7 +11,7 @@ Description:
|
||||
Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem
|
||||
are not present in /proc/pid/smaps. These fields represent
|
||||
the sum of the Pss field of each type (anon, file, shmem).
|
||||
For more details, see Documentation/filesystems/proc.txt
|
||||
For more details, see Documentation/filesystems/proc.rst
|
||||
and the procfs man page.
|
||||
|
||||
Typical output looks like this:
|
||||
|
@ -105,7 +105,7 @@ References
|
||||
----------
|
||||
|
||||
- http://lkml.org/lkml/2007/2/12/6
|
||||
- Documentation/filesystems/proc.txt (1.8)
|
||||
- Documentation/filesystems/proc.rst (1.8)
|
||||
|
||||
|
||||
Thanks
|
||||
|
@ -18,7 +18,7 @@ Mounting the root filesystem via NFS (nfsroot)
|
||||
In order to use a diskless system, such as an X-terminal or printer server for
|
||||
example, it is necessary for the root filesystem to be present on a non-disk
|
||||
device. This may be an initramfs (see
|
||||
Documentation/filesystems/ramfs-rootfs-initramfs.txt), a ramdisk (see
|
||||
Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see
|
||||
Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
|
||||
following text describes on how to use NFS for the root filesystem. For the rest
|
||||
of this text 'client' means the diskless system, and 'server' means the NFS
|
||||
|
@ -50,10 +50,10 @@ Attributes
|
||||
|
||||
Attributes of devices can be exported by a device driver through sysfs.
|
||||
|
||||
Please see Documentation/filesystems/sysfs.txt for more information
|
||||
Please see Documentation/filesystems/sysfs.rst for more information
|
||||
on how sysfs works.
|
||||
|
||||
As explained in Documentation/kobject.txt, device attributes must be
|
||||
As explained in Documentation/core-api/kobject.rst, device attributes must be
|
||||
created before the KOBJ_ADD uevent is generated. The only way to realize
|
||||
that is by defining an attribute group.
|
||||
|
||||
|
@ -121,4 +121,4 @@ device-specific data or tunable interfaces.
|
||||
|
||||
More information about the sysfs directory layout can be found in
|
||||
the other documents in this directory and in the file
|
||||
Documentation/filesystems/sysfs.txt.
|
||||
Documentation/filesystems/sysfs.rst.
|
||||
|
@ -74,7 +74,7 @@ are zeroed out and converted to written extents before being returned to avoid
|
||||
exposure of uninitialized data through mmap.
|
||||
|
||||
These filesystems may be used for inspiration:
|
||||
- ext2: see Documentation/filesystems/ext2.txt
|
||||
- ext2: see Documentation/filesystems/ext2.rst
|
||||
- ext4: see Documentation/filesystems/ext4/
|
||||
- xfs: see Documentation/admin-guide/xfs.rst
|
||||
|
||||
|
@ -67,4 +67,4 @@ See tools/testing/selftests/filesystems/dnotify_test.c for an example.
|
||||
NOTE
|
||||
----
|
||||
Beginning with Linux 2.6.13, dnotify has been replaced by inotify.
|
||||
See Documentation/filesystems/inotify.txt for more information on it.
|
||||
See Documentation/filesystems/inotify.rst for more information on it.
|
||||
|
@ -71,7 +71,7 @@ be allowed write access to a ramfs mount.
|
||||
|
||||
A ramfs derivative called tmpfs was created to add size limits, and the ability
|
||||
to write the data to swap space. Normal users can be allowed write access to
|
||||
tmpfs mounts. See Documentation/filesystems/tmpfs.txt for more information.
|
||||
tmpfs mounts. See Documentation/filesystems/tmpfs.rst for more information.
|
||||
|
||||
What is rootfs?
|
||||
---------------
|
||||
|
@ -20,7 +20,7 @@ a means to export kernel data structures, their attributes, and the
|
||||
linkages between them to userspace.
|
||||
|
||||
sysfs is tied inherently to the kobject infrastructure. Please read
|
||||
Documentation/kobject.txt for more information concerning the kobject
|
||||
Documentation/core-api/kobject.rst for more information concerning the kobject
|
||||
interface.
|
||||
|
||||
|
||||
|
@ -344,7 +344,7 @@ Here is the list of files under powerpc debugfs:
|
||||
|
||||
|
||||
NOTE:
|
||||
Please refer to Documentation/filesystems/debugfs.txt on
|
||||
Please refer to Documentation/filesystems/debugfs.rst on
|
||||
how to mount the debugfs filesystem.
|
||||
|
||||
|
||||
|
@ -33,7 +33,7 @@ interface.
|
||||
to a somewhat opaque API.
|
||||
|
||||
- If you're just exposing runtime system information, a new node in sysfs
|
||||
(see ``Documentation/filesystems/sysfs.txt``) or the ``/proc`` filesystem may
|
||||
(see ``Documentation/filesystems/sysfs.rst``) or the ``/proc`` filesystem may
|
||||
be more appropriate. However, access to these mechanisms requires that the
|
||||
relevant filesystem is mounted, which might not always be the case (e.g.
|
||||
in a namespaced/sandboxed/chrooted environment). Avoid adding any API to
|
||||
|
@ -39,7 +39,7 @@ vostra interfaccia.
|
||||
un qualche modo opaca.
|
||||
|
||||
- Se dovete esporre solo delle informazioni sul sistema, un nuovo nodo in
|
||||
sysfs (vedere ``Documentation/filesystems/sysfs.txt``) o
|
||||
sysfs (vedere ``Documentation/filesystems/sysfs.rst``) o
|
||||
in procfs potrebbe essere sufficiente. Tuttavia, l'accesso a questi
|
||||
meccanismi richiede che il filesystem sia montato, il che potrebbe non
|
||||
essere sempre vero (per esempio, in ambienti come namespace/sandbox/chroot).
|
||||
|
@ -1,4 +1,4 @@
|
||||
Chinese translated version of Documentation/filesystems/sysfs.txt
|
||||
Chinese translated version of Documentation/filesystems/sysfs.rst
|
||||
|
||||
If you have any comment or update to the content, please contact the
|
||||
original document maintainer directly. However, if you have a problem
|
||||
@ -10,7 +10,7 @@ Maintainer: Patrick Mochel <mochel@osdl.org>
|
||||
Mike Murphy <mamurph@cs.clemson.edu>
|
||||
Chinese maintainer: Fu Wei <tekkamanninja@gmail.com>
|
||||
---------------------------------------------------------------------
|
||||
Documentation/filesystems/sysfs.txt 的中文翻译
|
||||
Documentation/filesystems/sysfs.rst 的中文翻译
|
||||
|
||||
如果想评论或更新本文的内容,请直接联系原文档的维护者。如果你使用英文
|
||||
交流有困难的话,也可以向中文版维护者求助。如果本翻译更新不及时或者翻
|
||||
@ -40,7 +40,7 @@ sysfs 是一个最初基于 ramfs 且位于内存的文件系统。它提供导
|
||||
数据结构及其属性,以及它们之间的关联到用户空间的方法。
|
||||
|
||||
sysfs 始终与 kobject 的底层结构紧密相关。请阅读
|
||||
Documentation/kobject.txt 文档以获得更多关于 kobject 接口的
|
||||
Documentation/core-api/kobject.rst 文档以获得更多关于 kobject 接口的
|
||||
信息。
|
||||
|
||||
|
||||
|
@ -1374,7 +1374,7 @@ static void device_release(struct kobject *kobj)
|
||||
else if (dev->class && dev->class->dev_release)
|
||||
dev->class->dev_release(dev);
|
||||
else
|
||||
WARN(1, KERN_ERR "Device '%s' does not have a release() function, it is broken and must be fixed. See Documentation/kobject.txt.\n",
|
||||
WARN(1, KERN_ERR "Device '%s' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.\n",
|
||||
dev_name(dev));
|
||||
kfree(p);
|
||||
}
|
||||
|
@ -170,7 +170,7 @@ struct dpu_global_state
|
||||
*
|
||||
* Main debugfs documentation is located at,
|
||||
*
|
||||
* Documentation/filesystems/debugfs.txt
|
||||
* Documentation/filesystems/debugfs.rst
|
||||
*
|
||||
* @dpu_debugfs_setup_regset32: Initialize data for dpu_debugfs_create_regset32
|
||||
* @dpu_debugfs_create_regset32: Create 32-bit register dump file
|
||||
|
@ -166,7 +166,7 @@ config TMPFS
|
||||
space. If you unmount a tmpfs instance, everything stored therein is
|
||||
lost.
|
||||
|
||||
See <file:Documentation/filesystems/tmpfs.txt> for details.
|
||||
See <file:Documentation/filesystems/tmpfs.rst> for details.
|
||||
|
||||
config TMPFS_POSIX_ACL
|
||||
bool "Tmpfs POSIX Access Control Lists"
|
||||
|
@ -72,7 +72,7 @@ config CORE_DUMP_DEFAULT_ELF_HEADERS
|
||||
|
||||
The core dump behavior can be controlled per process using
|
||||
the /proc/PID/coredump_filter pseudo-file; this setting is
|
||||
inherited. See Documentation/filesystems/proc.txt for details.
|
||||
inherited. See Documentation/filesystems/proc.rst for details.
|
||||
|
||||
This config option changes the default setting of coredump_filter
|
||||
seen at boot time. If unsure, say Y.
|
||||
|
@ -12,7 +12,7 @@ config ADFS_FS
|
||||
|
||||
The ADFS partition should be the first partition (i.e.,
|
||||
/dev/[hs]d?1) on each of your drives. Please read the file
|
||||
<file:Documentation/filesystems/adfs.txt> for further details.
|
||||
<file:Documentation/filesystems/adfs.rst> for further details.
|
||||
|
||||
To compile this code as a module, choose M here: the module will be
|
||||
called adfs.
|
||||
|
@ -9,7 +9,7 @@ config AFFS_FS
|
||||
FFS partition on your hard drive. Amiga floppies however cannot be
|
||||
read with this driver due to an incompatibility of the floppy
|
||||
controller used in an Amiga and the standard floppy controller in
|
||||
PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
|
||||
PCs and workstations. Read <file:Documentation/filesystems/affs.rst>
|
||||
and <file:fs/affs/Changes>.
|
||||
|
||||
With this driver you can also mount disk files used by Bernd
|
||||
|
@ -8,7 +8,7 @@ config AFS_FS
|
||||
If you say Y here, you will get an experimental Andrew File System
|
||||
driver. It currently only supports unsecured read-only AFS access.
|
||||
|
||||
See <file:Documentation/filesystems/afs.txt> for more information.
|
||||
See <file:Documentation/filesystems/afs.rst> for more information.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@ -18,7 +18,7 @@ config AFS_DEBUG
|
||||
help
|
||||
Say Y here to make runtime controllable debugging messages appear.
|
||||
|
||||
See <file:Documentation/filesystems/afs.txt> for more information.
|
||||
See <file:Documentation/filesystems/afs.rst> for more information.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@ -37,6 +37,6 @@ config AFS_DEBUG_CURSOR
|
||||
the dmesg log if the server rotation algorithm fails to successfully
|
||||
contact a server.
|
||||
|
||||
See <file:Documentation/filesystems/afs.txt> for more information.
|
||||
See <file:Documentation/filesystems/afs.rst> for more information.
|
||||
|
||||
If unsure, say N.
|
||||
|
@ -11,7 +11,7 @@ config BFS_FS
|
||||
on your /stand slice from within Linux. You then also need to say Y
|
||||
to "UnixWare slices support", below. More information about the BFS
|
||||
file system is contained in the file
|
||||
<file:Documentation/filesystems/bfs.txt>.
|
||||
<file:Documentation/filesystems/bfs.rst>.
|
||||
|
||||
If you don't know what this is about, say N.
|
||||
|
||||
|
@ -9,7 +9,7 @@ config CRAMFS
|
||||
limited to 256MB file systems (with 16MB files), and doesn't support
|
||||
16/32 bits uid/gid, hard links and timestamps.
|
||||
|
||||
See <file:Documentation/filesystems/cramfs.txt> and
|
||||
See <file:Documentation/filesystems/cramfs.rst> and
|
||||
<file:fs/cramfs/README> for further information.
|
||||
|
||||
To compile this as a module, choose M here: the module will be called
|
||||
|
@ -7,7 +7,7 @@ config ECRYPT_FS
|
||||
select CRYPTO_MD5
|
||||
help
|
||||
Encrypted filesystem that operates on the VFS layer. See
|
||||
<file:Documentation/filesystems/ecryptfs.txt> to learn more about
|
||||
<file:Documentation/filesystems/ecryptfs.rst> to learn more about
|
||||
eCryptfs. Userspace components are required and can be
|
||||
obtained from <http://ecryptfs.sf.net>.
|
||||
|
||||
|
@ -6,7 +6,7 @@ config HFS_FS
|
||||
help
|
||||
If you say Y here, you will be able to mount Macintosh-formatted
|
||||
floppy disks and hard drive partitions with full read-write access.
|
||||
Please read <file:Documentation/filesystems/hfs.txt> to learn about
|
||||
Please read <file:Documentation/filesystems/hfs.rst> to learn about
|
||||
the available mount options.
|
||||
|
||||
To compile this file system support as a module, choose M here: the
|
||||
|
@ -9,7 +9,7 @@ config HPFS_FS
|
||||
write files to an OS/2 HPFS partition on your hard drive. OS/2
|
||||
floppies however are in regular MSDOS format, so you don't need this
|
||||
option in order to be able to read them. Read
|
||||
<file:Documentation/filesystems/hpfs.txt>.
|
||||
<file:Documentation/filesystems/hpfs.rst>.
|
||||
|
||||
To compile this file system support as a module, choose M here: the
|
||||
module will be called hpfs. If unsure, say N.
|
||||
|
@ -8,7 +8,7 @@ config ISO9660_FS
|
||||
long Unix filenames and symbolic links are also supported by this
|
||||
driver. If you have a CD-ROM drive and want to do more with it than
|
||||
just listen to audio CDs and watch its LEDs, say Y (and read
|
||||
<file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
|
||||
<file:Documentation/filesystems/isofs.rst> and the CD-ROM-HOWTO,
|
||||
available from <http://www.tldp.org/docs.html#howto>), thereby
|
||||
enlarging your kernel by about 27 KB; otherwise say N.
|
||||
|
||||
|
@ -3595,7 +3595,7 @@ EXPORT_SYMBOL(path_is_under);
|
||||
* file system may be mounted on put_old. After all, new_root is a mountpoint.
|
||||
*
|
||||
* Also, the current root cannot be on the 'rootfs' (initial ramfs) filesystem.
|
||||
* See Documentation/filesystems/ramfs-rootfs-initramfs.txt for alternatives
|
||||
* See Documentation/filesystems/ramfs-rootfs-initramfs.rst for alternatives
|
||||
* in this situation.
|
||||
*
|
||||
* Notes:
|
||||
|
@ -12,6 +12,6 @@ config INOTIFY_USER
|
||||
new features including multiple file events, one-shot support, and
|
||||
unmount notification.
|
||||
|
||||
For more information, see <file:Documentation/filesystems/inotify.txt>
|
||||
For more information, see <file:Documentation/filesystems/inotify.rst>
|
||||
|
||||
If unsure, say Y.
|
||||
|
@ -18,7 +18,7 @@ config NTFS_FS
|
||||
the Linux 2.4 kernel series is separately available as a patch
|
||||
from the project web site.
|
||||
|
||||
For more information see <file:Documentation/filesystems/ntfs.txt>
|
||||
For more information see <file:Documentation/filesystems/ntfs.rst>
|
||||
and <http://www.linux-ntfs.org/>.
|
||||
|
||||
To compile this file system support as a module, choose M here: the
|
||||
|
@ -21,7 +21,7 @@ config OCFS2_FS
|
||||
OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
|
||||
|
||||
For more information on OCFS2, see the file
|
||||
<file:Documentation/filesystems/ocfs2.txt>.
|
||||
<file:Documentation/filesystems/ocfs2.rst>.
|
||||
|
||||
config OCFS2_FS_O2CB
|
||||
tristate "O2CB Kernelspace Clustering"
|
||||
|
@ -23,7 +23,7 @@ config PROC_FS
|
||||
/proc" or the equivalent line in /etc/fstab does the job.
|
||||
|
||||
The /proc file system is explained in the file
|
||||
<file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
|
||||
<file:Documentation/filesystems/proc.rst> and on the proc(5) manpage
|
||||
("man 5 proc").
|
||||
|
||||
This option will enlarge your kernel by about 67 KB. Several
|
||||
@ -95,7 +95,7 @@ config PROC_CHILDREN
|
||||
default n
|
||||
help
|
||||
Provides a fast way to retrieve first level children pids of a task. See
|
||||
<file:Documentation/filesystems/proc.txt> for more information.
|
||||
<file:Documentation/filesystems/proc.rst> for more information.
|
||||
|
||||
Say Y if you are running any user-space software which takes benefit from
|
||||
this interface. For example, rkt is such a piece of software.
|
||||
|
@ -6,7 +6,7 @@ config ROMFS_FS
|
||||
This is a very small read-only file system mainly intended for
|
||||
initial ram disks of installation disks, but it could be used for
|
||||
other read-only media as well. Read
|
||||
<file:Documentation/filesystems/romfs.txt> for details.
|
||||
<file:Documentation/filesystems/romfs.rst> for details.
|
||||
|
||||
To compile this file system support as a module, choose M here: the
|
||||
module will be called romfs. Note that the file system of your
|
||||
|
@ -6,7 +6,7 @@
|
||||
* Copyright (c) 2007 SUSE Linux Products GmbH
|
||||
* Copyright (c) 2007 Tejun Heo <teheo@suse.de>
|
||||
*
|
||||
* Please see Documentation/filesystems/sysfs.txt for more information.
|
||||
* Please see Documentation/filesystems/sysfs.rst for more information.
|
||||
*/
|
||||
|
||||
#define pr_fmt(fmt) "sysfs: " fmt
|
||||
|
@ -6,7 +6,7 @@
|
||||
* Copyright (c) 2007 SUSE Linux Products GmbH
|
||||
* Copyright (c) 2007 Tejun Heo <teheo@suse.de>
|
||||
*
|
||||
* Please see Documentation/filesystems/sysfs.txt for more information.
|
||||
* Please see Documentation/filesystems/sysfs.rst for more information.
|
||||
*/
|
||||
|
||||
#include <linux/module.h>
|
||||
|
@ -6,7 +6,7 @@
|
||||
* Copyright (c) 2007 SUSE Linux Products GmbH
|
||||
* Copyright (c) 2007 Tejun Heo <teheo@suse.de>
|
||||
*
|
||||
* Please see Documentation/filesystems/sysfs.txt for more information.
|
||||
* Please see Documentation/filesystems/sysfs.rst for more information.
|
||||
*/
|
||||
|
||||
#include <linux/fs.h>
|
||||
|
@ -6,7 +6,7 @@
|
||||
* Copyright (c) 2007 SUSE Linux Products GmbH
|
||||
* Copyright (c) 2007 Tejun Heo <teheo@suse.de>
|
||||
*
|
||||
* Please see Documentation/filesystems/sysfs.txt for more information.
|
||||
* Please see Documentation/filesystems/sysfs.rst for more information.
|
||||
*/
|
||||
|
||||
#include <linux/fs.h>
|
||||
|
@ -28,7 +28,7 @@ config SYSV_FS
|
||||
tar" or preferably "info tar"). Note also that this option has
|
||||
nothing whatsoever to do with the option "System V IPC". Read about
|
||||
the System V file system in
|
||||
<file:Documentation/filesystems/sysv-fs.txt>.
|
||||
<file:Documentation/filesystems/sysv-fs.rst>.
|
||||
Saying Y here will enlarge your kernel by about 27 KB.
|
||||
|
||||
To compile this as a module, choose M here: the module will be called
|
||||
|
@ -9,7 +9,7 @@ config UDF_FS
|
||||
compatible with standard unix file systems, it is also suitable for
|
||||
removable USB disks. Say Y if you intend to mount DVD discs or CDRW's
|
||||
written in packet mode, or if you want to use UDF for removable USB
|
||||
disks. Please read <file:Documentation/filesystems/udf.txt>.
|
||||
disks. Please read <file:Documentation/filesystems/udf.rst>.
|
||||
|
||||
To compile this file system support as a module, choose M here: the
|
||||
module will be called udf.
|
||||
|
@ -7,7 +7,7 @@
|
||||
* Copyright (c) 2006-2008 Greg Kroah-Hartman <greg@kroah.com>
|
||||
* Copyright (c) 2006-2008 Novell Inc.
|
||||
*
|
||||
* Please read Documentation/kobject.txt before using the kobject
|
||||
* Please read Documentation/core-api/kobject.rst before using the kobject
|
||||
* interface, ESPECIALLY the parts about reference counts and object
|
||||
* destructors.
|
||||
*/
|
||||
|
@ -8,7 +8,7 @@
|
||||
*
|
||||
* Split from kobject.h by David Howells (dhowells@redhat.com)
|
||||
*
|
||||
* Please read Documentation/kobject.txt before using the kobject
|
||||
* Please read Documentation/core-api/kobject.rst before using the kobject
|
||||
* interface, ESPECIALLY the parts about reference counts and object
|
||||
* destructors.
|
||||
*/
|
||||
|
@ -141,7 +141,7 @@ struct rchan_callbacks
|
||||
* cause relay_open() to create a single global buffer rather
|
||||
* than the default set of per-cpu buffers.
|
||||
*
|
||||
* See Documentation/filesystems/relay.txt for more info.
|
||||
* See Documentation/filesystems/relay.rst for more info.
|
||||
*/
|
||||
struct dentry *(*create_buf_file)(const char *filename,
|
||||
struct dentry *parent,
|
||||
|
@ -7,7 +7,7 @@
|
||||
* Copyright (c) 2007 SUSE Linux Products GmbH
|
||||
* Copyright (c) 2007 Tejun Heo <teheo@suse.de>
|
||||
*
|
||||
* Please see Documentation/filesystems/sysfs.txt for more information.
|
||||
* Please see Documentation/filesystems/sysfs.rst for more information.
|
||||
*/
|
||||
|
||||
#ifndef _SYSFS_H_
|
||||
|
@ -1,7 +1,7 @@
|
||||
/*
|
||||
* Public API and common code for kernel->userspace relay file support.
|
||||
*
|
||||
* See Documentation/filesystems/relay.txt for an overview.
|
||||
* See Documentation/filesystems/relay.rst for an overview.
|
||||
*
|
||||
* Copyright (C) 2002-2005 - Tom Zanussi (zanussi@us.ibm.com), IBM Corp
|
||||
* Copyright (C) 1999-2005 - Karim Yaghmour (karim@opersys.com)
|
||||
|
@ -6,7 +6,7 @@
|
||||
* Copyright (c) 2006-2007 Greg Kroah-Hartman <greg@kroah.com>
|
||||
* Copyright (c) 2006-2007 Novell Inc.
|
||||
*
|
||||
* Please see the file Documentation/kobject.txt for critical information
|
||||
* Please see the file Documentation/core-api/kobject.rst for critical information
|
||||
* about using the kobject interface.
|
||||
*/
|
||||
|
||||
@ -670,7 +670,7 @@ static void kobject_cleanup(struct kobject *kobj)
|
||||
kobject_name(kobj), kobj, __func__, kobj->parent);
|
||||
|
||||
if (t && !t->release)
|
||||
pr_debug("kobject: '%s' (%p): does not have a release() function, it is broken and must be fixed. See Documentation/kobject.txt.\n",
|
||||
pr_debug("kobject: '%s' (%p): does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.\n",
|
||||
kobject_name(kobj), kobj);
|
||||
|
||||
/* send "remove" if the caller did not do it but sent "add" */
|
||||
|
Loading…
Reference in New Issue
Block a user