Home
last modified time | relevance | path

Searched refs:lists (Results 1 – 200 of 253) sorted by relevance

12

/linux-4.4.14/fs/xfs/
Dxfs_mru_cache.c105 struct list_head *lists; /* Array of lists, one per grp. */ member
156 lru_list = mru->lists + mru->lru_grp; in _xfs_mru_cache_migrate()
182 lru_list = mru->lists + ((mru->lru_grp + grp) % mru->grp_count); in _xfs_mru_cache_migrate()
226 list_add_tail(&elem->list_node, mru->lists + grp); in _xfs_mru_cache_list_insert()
283 ASSERT(mru && mru->lists); in _xfs_mru_cache_reap()
284 if (!mru || !mru->lists) in _xfs_mru_cache_reap()
351 mru->lists = kmem_zalloc(mru->grp_count * sizeof(*mru->lists), KM_SLEEP); in xfs_mru_cache_create()
353 if (!mru->lists) { in xfs_mru_cache_create()
359 INIT_LIST_HEAD(mru->lists + grp); in xfs_mru_cache_create()
376 if (err && mru && mru->lists) in xfs_mru_cache_create()
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-cxl11 Contact: linuxppc-dev@lists.ozlabs.org
22 Contact: linuxppc-dev@lists.ozlabs.org
33 Contact: linuxppc-dev@lists.ozlabs.org
43 Contact: linuxppc-dev@lists.ozlabs.org
51 Contact: linuxppc-dev@lists.ozlabs.org
59 Contact: linuxppc-dev@lists.ozlabs.org
69 Contact: linuxppc-dev@lists.ozlabs.org
82 Contact: linuxppc-dev@lists.ozlabs.org
90 Contact: linuxppc-dev@lists.ozlabs.org
97 Contact: linuxppc-dev@lists.ozlabs.org
[all …]
Dsysfs-class-mtd4 Contact: linux-mtd@lists.infradead.org
12 Contact: linux-mtd@lists.infradead.org
22 Contact: linux-mtd@lists.infradead.org
30 Contact: linux-mtd@lists.infradead.org
39 Contact: linux-mtd@lists.infradead.org
48 Contact: linux-mtd@lists.infradead.org
58 Contact: linux-mtd@lists.infradead.org
71 Contact: linux-mtd@lists.infradead.org
79 Contact: linux-mtd@lists.infradead.org
88 Contact: linux-mtd@lists.infradead.org
[all …]
Dsysfs-bus-event_source-devices-hv_gpci3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
12 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
19 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
26 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
33 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
40 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Dsysfs-bus-event_source-devices-hv_24x73 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
6 hypervisor on POWER7 and 8 systems. This catalog lists events
13 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
20 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
27 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
38 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Dsysfs-class16 udev <linux-hotplug-devel@lists.sourceforge.net>
Dsysfs-driver-pciback4 Contact: xen-devel@lists.xenproject.org
Dsysfs-kernel-vmcoreinfo5 Kexec Mailing List <kexec@lists.infradead.org>
Ddebugfs-olpc4 Contact: devel@lists.laptop.org
Dsysfs-devices25 udev <linux-hotplug-devel@lists.sourceforge.net>
Dsysfs-kernel-slab37 The alloc_calls file is read-only and lists the kernel code
220 The free_calls file is read-only and lists the locations of
Dsysfs-devices-system-cpu196 Contact: kexec@lists.infradead.org
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-tpm4 Contact: tpmdd-devel@lists.sf.net
12 Contact: tpmdd-devel@lists.sf.net
24 Contact: tpmdd-devel@lists.sf.net
32 Contact: tpmdd-devel@lists.sf.net
49 Contact: tpmdd-devel@lists.sf.net
72 Contact: tpmdd-devel@lists.sf.net
81 Contact: tpmdd-devel@lists.sf.net
89 Contact: tpmdd-devel@lists.sf.net
112 Contact: tpmdd-devel@lists.sf.net
164 Contact: tpmdd-devel@lists.sf.net
[all …]
Dsysfs-bus-firewire4 Contact: linux1394-devel@lists.sourceforge.net
23 Contact: linux1394-devel@lists.sourceforge.net
45 Contact: linux1394-devel@lists.sourceforge.net
56 Contact: linux1394-devel@lists.sourceforge.net
74 Contact: linux1394-devel@lists.sourceforge.net
118 Contact: linux1394-devel@lists.sourceforge.net
Dsysfs-bus-usb39 PowerTOP <powertop@lists.01.org>
58 PowerTOP <powertop@lists.01.org>
Dfirewire-cdev4 Contact: linux1394-devel@lists.sourceforge.net
Dsysfs-driver-ib_srp50 implementations support partial memory descriptor lists the
/linux-4.4.14/
DMAINTAINERS40 PLEASE CC: the maintainers and mailing lists that are generated
193 L: v9fs-developer@lists.sourceforge.net
494 L: linux-afs@lists.infradead.org
582 L: nios2-dev@lists.rocketboards.org (moderated for non-subscribers)
595 L: nios2-dev@lists.rocketboards.org (moderated for non-subscribers)
602 L: nios2-dev@lists.rocketboards.org (moderated for non-subscribers)
624 L: linux-geode@lists.infradead.org (moderated for non-subscribers)
630 L: linux-geode@lists.infradead.org (moderated for non-subscribers)
640 L: iommu@lists.linux-foundation.org
648 L: dri-devel@lists.freedesktop.org
[all …]
DREPORTING-BUGS33 maintainer doesn't answer, then expand your scope to mailing lists like
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-vt8500.txt23 Each pin configuration node lists the pin(s) to which it applies, and one or
26 listed. In other words, a subnode that lists only a mux function implies no
27 information about any pull configuration. Similarly, a subnode that lists only
Dbrcm,bcm2835-gpio.txt32 Each pin configuration node lists the pin(s) to which it applies, and one or
35 listed. In other words, a subnode that lists only a mux function implies no
36 information about any pull configuration. Similarly, a subnode that lists only
Dlantiq,pinctrl-falcon.txt22 other words, a subnode that lists a mux function but no pin configuration
Dqcom,apq8064-pinctrl.txt31 other words, a subnode that lists a mux function but no pin configuration
Dqcom,msm8660-pinctrl.txt31 other words, a subnode that lists a mux function but no pin configuration
Dqcom,ipq8064-pinctrl.txt31 other words, a subnode that lists a mux function but no pin configuration
Dpinctrl-palmas.txt26 other words, a subnode that lists a mux function but no pin configuration
Dqcom,msm8974-pinctrl.txt31 other words, a subnode that lists a mux function but no pin configuration
Dlantiq,pinctrl-xway.txt22 other words, a subnode that lists a mux function but no pin configuration
Dimg,tz1090-pdc-pinctrl.txt22 other words, a subnode that lists a mux function but no pin configuration
Dnvidia,tegra124-xusb-padctl.txt39 words, if a subnode that lists a function but no pin configuration parameters
Dqcom,msm8960-pinctrl.txt63 other words, a subnode that lists a mux function but no pin configuration
Dqcom,apq8084-pinctrl.txt63 other words, a subnode that lists a mux function but no pin configuration
Dqcom,msm8916-pinctrl.txt63 other words, a subnode that lists a mux function but no pin configuration
Dqcom,pmic-mpp.txt62 other words, a subnode that lists a mux function but no pin configuration
Dqcom,pmic-gpio.txt62 other words, a subnode that lists a mux function but no pin configuration
Dnvidia,tegra20-pinmux.txt22 other words, a subnode that lists a mux function but no pin configuration
Dnvidia,tegra210-pinmux.txt23 other words, a subnode that lists a mux function but no pin configuration
Dimg,tz1090-pinctrl.txt22 other words, a subnode that lists a mux function but no pin configuration
/linux-4.4.14/Documentation/ko_KR/
DHOWTO356 https://lists.linux-foundation.org/mailman/listinfo/bugme-new
357 https://lists.linux-foundation.org/mailman/listinfo/bugme-janitors
367 http://vger.kernel.org/vger-lists.html#linux-kernel
380 http://vger.kernel.org/vger-lists.html
/linux-4.4.14/Documentation/driver-model/
Dbus.txt63 The lists of devices and drivers are intended to replace the local
64 lists that many buses keep. They are lists of struct devices and
66 lists as they please, but conversion to the bus-specific type may be
Dclass.txt69 class, iterate over the device lists of each driver in the class.
Dporting.txt432 the device and driver lists. This can be used by the bus driver
434 lists the bus maintains.
/linux-4.4.14/Documentation/cpu-freq/
Dindex.txt39 http://vger.kernel.org/vger-lists.html#linux-pm and follow the
51 * http://vger.kernel.org/vger-lists.html#cpufreq
/linux-4.4.14/Documentation/ja_JP/
DHOWTO404 http://lists.linux-foundation.org/mailman/listinfo/bugme-new
405 http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors
413 http://vger.kernel.org/vger-lists.html#linux-kernel
429 http://vger.kernel.org/vger-lists.html
DSubmittingPatches200 <http://vger.kernel.org/vger-lists.html>
/linux-4.4.14/scripts/gdb/
Dvmlinux-gdb.py31 import linux.lists
/linux-4.4.14/Documentation/zh_CN/
DHOWTO350 https://lists.linux-foundation.org/mailman/listinfo/bugme-new
351 https://lists.linux-foundation.org/mailman/listinfo/bugme-janitors
359 http://vger.kernel.org/vger-lists.html#linux-kernel
370 http://vger.kernel.org/vger-lists.html
DSubmittingPatches141 Majordomo lists of VGER.KERNEL.ORG at:
142 <http://vger.kernel.org/vger-lists.html>
/linux-4.4.14/drivers/staging/mt29f_spinand/
DTODO13 linux-mtd@lists.infradead.org
/linux-4.4.14/Documentation/devicetree/
Dtodo.txt4 - Switch from custom lists to (h)list_head for nodes and properties structure
D00-INDEX5 https://lists.ozlabs.org/listinfo/devicetree-discuss
/linux-4.4.14/Documentation/cgroups/
Dcpuacct.txt17 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
33 cpuacct.stat file lists a few statistics which further divide the
Dhugetlb.txt17 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
Dnet_prio.txt23 the system. '/sys/fs/cgroup/net_prio/tasks' lists the tasks in this cgroup.
/linux-4.4.14/Documentation/features/io/sg-chain/
Darch-support.txt4 # description: arch supports chained scatter-gather lists
/linux-4.4.14/Documentation/networking/
Dbridge.txt14 (more info https://lists.linux-foundation.org/mailman/listinfo/bridge).
Dirda.txt10 irda-users@lists.sourceforge.net
Di40e.txt76 e1000-eedc@lists.sourceforge.net for DCB information.
117 to the issue to e1000-devel@lists.sourceforge.net and copy
Di40evf.txt47 to the issue to e1000-devel@lists.sf.net
Dnetdev-FAQ.txt12 of traffic have their own specific mailing lists.
14 The netdev list is managed (like many other Linux mailing lists) through
18 http://www.spinics.net/lists/netdev/
197 use the mailing lists and not reach out directly. If you aren't OK with
199 http://oss-security.openwall.org/wiki/mailing-lists/distros
Dixgbevf.txt52 to the issue to e1000-devel@lists.sf.net
Digbvf.txt80 to the issue to e1000-devel@lists.sf.net
Digb.txt129 to the issue to e1000-devel@lists.sf.net
Dcan.txt14 3.1 receive lists
167 3.1 receive lists
173 high efficient receive lists for this reason. If e.g. a user space
180 To optimize the CPU usage at runtime the receive lists are split up
181 into several specific lists per device that match the requested
478 The CAN filters are processed in per-device filter lists at CAN frame
480 while walking through the filter lists the CAN core provides an optimized
870 lists to deliver received CAN frames to CAN protocol modules. These
871 receive lists, their filters and the count of filter matches can be
Dixgbe.txt285 e1000-eedc@lists.sourceforge.net for DCB information.
349 to the issue to e1000-devel@lists.sf.net
De100.txt183 issue to e1000-devel@lists.sourceforge.net.
Dbatman-adv.txt197 at https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n)
De1000e.txt312 to the issue to e1000-devel@lists.sf.net
/linux-4.4.14/Documentation/devicetree/bindings/extcon/
Dextcon-arizona.txt6 This document lists Extcon specific bindings, see the primary binding document:
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Darizona-regulator.txt6 This document lists regulator specific bindings, see the primary binding
/linux-4.4.14/Documentation/ABI/removed/
Ddv13943 Contact: linux1394-devel@lists.sourceforge.net
Draw13943 Contact: linux1394-devel@lists.sourceforge.net
Dvideo13943 Contact: linux1394-devel@lists.sourceforge.net
/linux-4.4.14/include/linux/
Dmm_inline.h30 list_add(&page->lru, &lruvec->lists[lru]); in add_page_to_lru_list()
Dmmzone.h217 struct list_head lists[NR_LRU_LISTS]; member
258 struct list_head lists[MIGRATE_PCPTYPES]; member
/linux-4.4.14/Documentation/development-process/
D2.Process288 lists when they are assembled; they can be downloaded from:
310 TODO file should be present in the directory as well. The TODO file lists
374 lists. It is hard to be a fully-functioning member of the community
375 without joining at least one list somewhere. But Linux mailing lists also
378 lists, or both.
380 Most kernel mailing lists are run on vger.kernel.org; the master list can
383 http://vger.kernel.org/vger-lists.html
385 There are lists hosted elsewhere, though; a number of them are at
386 lists.redhat.com.
411 - When responding to linux-kernel email (or that on other lists) preserve
[all …]
D1.Intro26 discussion of tools and mailing lists. Developers wanting to get started
269 mailing lists. Such questions will normally receive no shortage of
274 obtained on technical mailing lists is a risky affair.
D3.Early-stage124 the right maintainer. For mailing lists, the best approach is to look in
/linux-4.4.14/Documentation/RCU/
Drcuref.txt1 Reference-count design for elements of lists/arrays protected by RCU.
12 Reference counting on elements of lists which are protected by traditional
D00-INDEX22 - Reference-count design for elements of lists/arrays protected by RCU
Drcu.txt12 file for more information on using RCU with linked lists.
Drculist_nulls.txt1 Using hlist_nulls to protect read-mostly linked lists and
DarrayRCU.txt4 Although RCU is more commonly used to protect linked lists, it can
Dchecklist.txt158 in their respective types of RCU-protected lists.
161 type of RCU-protected linked lists.
DlistRCU.txt4 One of the best applications of RCU is to protect read-mostly linked lists
Drcu_dereference.txt139 RCU-protected circular linked lists.
/linux-4.4.14/mm/
Dmmzone.c95 INIT_LIST_HEAD(&lruvec->lists[lru]); in lruvec_init()
Dswap.c454 list_move_tail(&page->lru, &lruvec->lists[lru]); in pagevec_move_tail_fn()
793 list_move_tail(&page->lru, &lruvec->lists[lru]); in lru_deactivate_file_fn()
Dpage_alloc.c825 list = &pcp->lists[migratetype]; in free_pcppages_bulk()
2077 list_add(&page->lru, &pcp->lists[migratetype]); in free_hot_cold_page()
2079 list_add_tail(&page->lru, &pcp->lists[migratetype]); in free_hot_cold_page()
2225 list = &pcp->lists[migratetype]; in buffered_rmqueue()
4647 INIT_LIST_HEAD(&pcp->lists[migratetype]); in pageset_init()
Dvmscan.c1361 struct list_head *src = &lruvec->lists[lru]; in isolate_lru_pages()
1739 list_move(&page->lru, &lruvec->lists[lru]); in move_active_pages_to_lru()
/linux-4.4.14/Documentation/sysctl/
Dnet.txt242 /proc/net/atalk_iface lists all the interfaces configured for appletalk.It
247 /proc/net/atalk_route lists each known network route. It lists the target
257 The IPX protocol does, however, provide proc/net/ipx. This lists each IPX
266 The /proc/net/ipx_interface file lists all IPX interfaces. For each interface
/linux-4.4.14/Documentation/vm/
Dunevictable-lru.txt62 will spend a lot of time scanning the LRU lists looking for the small fraction
101 lists. If we were to maintain pages elsewhere than on an LRU-like list,
112 lists and statistics originally proposed and posted by Christoph Lameter.
129 list as a result of the "arrayification" of the per-zone LRU lists (one per
213 active/inactive LRU lists for vmscan to deal with. vmscan checks for such
373 are inherently unevictable and are not managed on the LRU lists.
432 A page that is being migrated has been isolated from the LRU lists and is held
525 of the active or inactive LRU lists. This could happen if, for example, a task
583 active/inactive lru lists. Note that these pages do not have PageUnevictable
587 Some examples of these unevictable pages on the LRU lists are:
[all …]
Dnuma69 subsystem, complete with its own free page lists, in-use page lists, usage
Dactive_mm.txt13 > discussed on the mailing lists---I just returned from vacation and
Didle_page_tracking.txt71 because a process needs filesystem metadata stored in it (e.g. lists a
Dpage_migration65 pages and moving them into lists. This is done by
Dpagemap.txt139 5. LRU page is in one of the LRU lists
Dslub.txt16 data and perform operation on the slabs. By default slabinfo only lists
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dprcm.txt3 Power Reset and Clock Manager lists the device clocks and clockdomains under
/linux-4.4.14/Documentation/
Dhw_random.txt39 "rng_available" attribute lists the hardware-specific drivers
40 available, while "rng_current" lists the one which is currently
DHOWTO63 people on the mailing lists are not lawyers, and you should not rely on
312 subject to review which primarily happens on mailing lists (see the
362 http://lists.linux-foundation.org/mailman/listinfo/bugme-new
363 http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors
367 Mailing lists
373 http://vger.kernel.org/vger-lists.html#linux-kernel
384 MAINTAINERS file for a list of what these lists are for the different
387 Many of the lists are hosted on kernel.org. Information on them can be
389 http://vger.kernel.org/vger-lists.html
391 Please remember to follow good behavioral habits when using the lists.
[all …]
DCodeOfConflict18 <tab@lists.linux-foundation.org>, or the individual members, and they
Dvgaarbiter.txt190 [1] http://lists.freedesktop.org/archives/xorg/2005-March/006663.html
191 [2] http://lists.freedesktop.org/archives/xorg/2005-March/006745.html
192 [3] http://lists.freedesktop.org/archives/xorg/2007-October/029507.html
Dvme_api.txt237 API introduces the concept of DMA lists. Each DMA list is a link-list which can
238 be passed to a DMA controller. Multiple lists can be created, extended,
245 The following functions are provided to create and destroy DMA lists. Execution
DIntel-IOMMU.txt21 ACPI enumerates and lists the different DMA engines in the platform, and
DSubmittingPatches278 spam unrelated lists, though.
280 Many kernel-related lists are hosted on vger.kernel.org; you can find a
281 list of them at http://vger.kernel.org/vger-lists.html. There are
282 kernel-related lists hosted elsewhere as well, though.
284 Do not send more than 15 patches at once to the vger mailing lists!!!
295 obviously, the patch should not be sent to any public lists.
362 Large changes are not appropriate for mailing lists, and some
Dmen-chameleon-bus.txt58 header lists the device id, PCI BAR, offset from the beginning of the PCI
Dxz.txt115 kernel-related mailing lists, so if there's something I should know,
Dsysfs-rules.txt104 not contain any device directories themselves, but only flat lists of
Drobust-futex-ABI.txt49 compatibility mode, will attempt to process both lists on each task
Demail-clients.txt53 mailing lists.
Dkernel-doc-nano-HOWTO.txt104 breaks. So presenting carefully formatted lists within these
Dunshare.txt58 from default shared namespace. The following lists two use-cases
Dsysrq.txt103 'q' - Will dump per CPU lists of all armed hrtimers (but NOT regular
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME41 bttv uses the PCI Subsystem ID to autodetect the card type. lspci lists
67 http://vger.kernel.org/vger-lists.html#linux-media
/linux-4.4.14/arch/s390/kvm/
Dinterrupt.c640 inti = list_first_entry_or_null(&fi->lists[FIRQ_LIST_PFAULT], in __deliver_pfault_done()
647 if (list_empty(&fi->lists[FIRQ_LIST_PFAULT])) in __deliver_pfault_done()
682 inti = list_first_entry_or_null(&fi->lists[FIRQ_LIST_VIRTIO], in __deliver_virtio()
697 if (list_empty(&fi->lists[FIRQ_LIST_VIRTIO])) in __deliver_virtio()
732 isc_list = &fi->lists[irq_type - IRQ_PEND_IO_ISC_0]; in __deliver_io()
1183 struct list_head *isc_list = &fi->lists[FIRQ_LIST_IO_ISC_0 + isc]; in get_io_int()
1261 list_add_tail(&inti->list, &fi->lists[FIRQ_LIST_VIRTIO]); in __inject_virtio()
1279 list_add_tail(&inti->list, &fi->lists[FIRQ_LIST_PFAULT]); in __inject_pfault_done()
1315 list = &fi->lists[FIRQ_LIST_IO_ISC_0 + isc]; in __inject_io()
1605 clear_irq_list(&fi->lists[i]); in kvm_s390_clear_float_irqs()
[all …]
/linux-4.4.14/Documentation/security/
Dapparmor.txt36 Mailing List - apparmor@lists.ubuntu.com
Dtomoyo.txt25 Below lists are chosen from three aspects.
/linux-4.4.14/Documentation/blockdev/drbd/
Ddata-structure-v9.txt29 linked lists. There are back pointers from peer_devices to their connections a
/linux-4.4.14/Documentation/i2c/busses/
Di2c-nforce250 Asus A7N8X lists two SMBuses, both of which are supported by this driver.
/linux-4.4.14/Documentation/dvb/
Dreadme.txt8 see http://linuxtv.org/lists.php. Please check
Dfaq.txt21 one of the supplied channel lists, or you can create a new one
/linux-4.4.14/Documentation/video4linux/
Domap4_camera.txt57 [3] http://www.spinics.net/lists/linux-media/msg44370.html
Duvcvideo.txt8 linux-uvc-devel@lists.berlios.de.
DZoran478 an email to <mjpeg-users@lists.sf.net>, for developers (i.e. if you want to
479 help programming), send an email to <mjpeg-developer@lists.sf.net>. See
/linux-4.4.14/crypto/asymmetric_keys/
Dpkcs7.asn141 -- Certificates and certificate lists
/linux-4.4.14/firmware/
DREADME.AddingFirmware25 and also cc: to related mailing lists.
/linux-4.4.14/arch/arm/boot/dts/
Dam335x-bone-common.dtsi300 * http://www.spinics.net/lists/linux-omap/msg118585.html
301 * http://www.spinics.net/lists/linux-omap/msg118615.html
Dkirkwood-b3.dts15 * http://lists.debian.org/debian-arm/2012/08/msg00128.html
/linux-4.4.14/drivers/clk/
Dclk.c2007 struct hlist_head **lists = (struct hlist_head **)s->private; in clk_summary_show() local
2014 for (; *lists; lists++) in clk_summary_show()
2015 hlist_for_each_entry(c, *lists, child_node) in clk_summary_show()
2071 struct hlist_head **lists = (struct hlist_head **)s->private; in clk_dump() local
2077 for (; *lists; lists++) { in clk_dump()
2078 hlist_for_each_entry(c, *lists, child_node) { in clk_dump()
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dmux.txt10 By default the "clocks" property lists the parents in the same order
Ddpll.txt37 - clocks : link phandles of parent clocks, first entry lists reference clock
/linux-4.4.14/Documentation/arm/sunxi/
DREADME4 This document lists all the ARM Allwinner SoCs that are currently
/linux-4.4.14/fs/ocfs2/
DKconfig20 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
/linux-4.4.14/Documentation/devicetree/bindings/display/
Drenesas,du.txt41 The following table lists for each supported model the port number
/linux-4.4.14/Documentation/rapidio/
Dtsi721.txt41 1.1.0 - DMA operations re-worked to support data scatter/gather lists larger
Drapidio.txt52 structure. Devices form one global device list and per-network device lists
72 data structure. This structure includes lists of all devices and local master
/linux-4.4.14/Documentation/w1/slaves/
Dw1_therm49 resistor). The DS18b20 temperature sensor specification lists a
/linux-4.4.14/drivers/atm/
Dnicstarmac.copyright21 * expects the Linux ATM stack to support scatter-gather lists
/linux-4.4.14/Documentation/kbuild/
Dkconfig.txt160 This lists all config symbols that contain "hotplug",
220 lists all config symbol entries that contain "hotplug" in
Dmakefiles.txt80 .config file to construct various file lists used by kbuild to build
151 in the $(obj-y) lists. These lists depend on the kernel
159 the lists are allowed: the first instance will be linked into
632 $(<executable>-objs) lists all objects used to link the final
1002 $(head-y) lists objects to be linked first in vmlinux.
1003 $(libs-y) lists directories where a lib.a archive can be located.
Dkbuild.txt11 This file lists all modules that are built into the kernel. This is used
Dmodules.txt454 1) It lists all exported symbols from vmlinux and all modules.
455 2) It lists the CRC if CONFIG_MODVERSIONS is enabled.
/linux-4.4.14/fs/jffs2/
DREADME.Locking74 This is used to serialise access to the eraseblock lists, to the
75 per-eraseblock lists of physical jffs2_raw_node_ref structures, and
/linux-4.4.14/Documentation/scsi/
Ddc395x.txt17 http://lists.twibble.org/mailman/listinfo/dc395x/
Dscsi-changer.txt73 I don't have any device lists, neither black-list nor white-list. Thus
Dosd.txt110 associated get+set of attributes-lists. Other combinations very on the same
Dscsi_eh.txt33 scmd has two list_head's to link itself into lists. The two are
36 discussion. The latter is used for completion and EH lists and unless
DChangeLog.1992-199732 * scsi.c (scsi_proc_info): /proc/scsi/scsi now also lists all
1251 we want to use linked lists instead of arrays because it is easier
1336 larger SG lists.
1387 adapter. The buslogic board apparently supports large SG lists,
/linux-4.4.14/Documentation/filesystems/
Dudf.txt32 undelete Show deleted files in lists.
Doverlayfs.txt81 Only the lists of names from directories are merged. Other content
106 lower directories are each read and the name lists merged in the
Ddlmfs.txt10 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
Docfs2.txt13 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
Dsquashfs.txt15 Mailing list: squashfs-devel@lists.sourceforge.net
226 The xattr lists are packed into compressed 8K metadata blocks.
D9p.txt148 There are user and developer mailing lists available through the v9fs project
Dafs.txt137 (*) A "cells" file that lists cells currently known to the afs module and
Dxfs-self-describing-metadata.txt48 understanding how things like cross linked block lists (e.g. sibling
158 sibling pointer lists). Hence we still need stateful checking in the main code
Dbtrfs.txt233 http://vger.kernel.org/vger-lists.html#linux-btrfs
Dnilfs2.txt30 List info: http://vger.kernel.org/vger-lists.html#linux-nilfs
Dpath-lookup.txt84 The hash lists are RCU protected, so list walking is not serialised with
100 Back to the rename case. In usual RCU protected lists, the only operations that
Dntfs.txt225 list at sourceforge: linux-ntfs-dev@lists.sourceforge.net
422 linux-ntfs developers list linux-ntfs-dev@lists.sourceforge.net or drop in on
Df2fs.txt26 >> linux-f2fs-devel@lists.sourceforge.net
357 inode lists, and summary entries of current active segments.
/linux-4.4.14/fs/nilfs2/
Dbtree.c2098 struct list_head *lists, in nilfs_btree_add_dirty_buffer() argument
2123 list_for_each(head, &lists[level]) { in nilfs_btree_add_dirty_buffer()
2137 struct list_head lists[NILFS_BTREE_LEVEL_MAX]; in nilfs_btree_lookup_dirty_buffers() local
2146 INIT_LIST_HEAD(&lists[level]); in nilfs_btree_lookup_dirty_buffers()
2157 lists, bh); in nilfs_btree_lookup_dirty_buffers()
2167 list_splice_tail(&lists[level], listp); in nilfs_btree_lookup_dirty_buffers()
/linux-4.4.14/Documentation/hwmon/
Dcoretemp52 Appendix A. Known TjMax lists (TBD):
/linux-4.4.14/sound/core/
Dcontrol.c1605 static int _snd_ctl_register_ioctl(snd_kctl_ioctl_func_t fcn, struct list_head *lists) in _snd_ctl_register_ioctl() argument
1614 list_add_tail(&pn->list, lists); in _snd_ctl_register_ioctl()
1648 struct list_head *lists) in _snd_ctl_unregister_ioctl() argument
1655 list_for_each_entry(p, lists, list) { in _snd_ctl_unregister_ioctl()
/linux-4.4.14/Documentation/arm/
DPorting1 Taken from list archive at http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-July/00406…
DREADME47 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
DBooting51 option to the kernel via the tagged lists specifying the port, and
/linux-4.4.14/Documentation/usb/
Drio.txt51 There is also a mailing list: rio500-users@lists.sourceforge.net
Dgadget-testing.txt460 http://www.spinics.net/lists/linux-usb/msg85689.html
481 http://www.spinics.net/lists/linux-usb/msg85690.html
722 http://www.spinics.net/lists/linux-usb/msg99220.html
Dgadget_configfs.txt52 http://www.spinics.net/lists/linux-usb/msg76388.html)
DWUSB-Design-overview.txt46 4. Device lists
238 Device lists
Dmass-storage.txt34 This parameter lists paths to files or block devices used for
/linux-4.4.14/tools/build/Documentation/
DBuild.txt71 ex-y += b.o # duplicates in the lists are allowed
/linux-4.4.14/Documentation/ia64/
Dxen.txt134 "git branch -r" to get the branch lists.
Dmca.txt10 by locks is indeterminate, including linked lists.
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs41-server.txt27 The table below, taken from the NFSv4.1 document, lists
Dnfs-rdma.txt37 nfs-rdma-devel@lists.sourceforge.net
Drpc-cache.txt72 Optional. Used to provide a /proc file that lists the
/linux-4.4.14/arch/s390/include/asm/
Dkvm_host.h457 struct list_head lists[FIRQ_LIST_COUNT]; member
/linux-4.4.14/Documentation/trace/
Devents-kmem.txt88 lists should be a larger size. Finally, large amounts of refills on one CPU
Dtracepoint-analysis.txt204 are freed to the main allocator from the per-CPU lists, it recognises
/linux-4.4.14/Documentation/laptops/
Dasus-laptop.txt255 acpi4asus-user@lists.sourceforge.net
Ddisk-shock-protection.txt146 originally published by Jon Escombe <lists@dresco.co.uk>. My efforts
Dthinkpad-acpi.txt804 a report to ibm-acpi-devel@lists.sourceforge.net is appreciated.
1116 please report this to ibm-acpi-devel@lists.sourceforge.net, so that we
1126 ibm-acpi-devel@lists.sourceforge.net.
1428 not, please contact ibm-acpi-devel@lists.sourceforge.net with a report.
/linux-4.4.14/Documentation/locking/
Dspinlocks.txt72 linked lists, especially searching for entries without changing the list
/linux-4.4.14/drivers/usb/usbip/
Dusbip_protocol.txt12 the OP_REP_DEVLIST packet which lists the exported USB devices. Finally the
/linux-4.4.14/Documentation/power/
Dpower_supply_class.txt171 External power supply (AC) lists supplicants (batteries) names in
Dpm_qos_interface.txt93 For each device, there are three lists of PM QoS requests. Two of them are
Dbasic-pm-debugging.txt228 to RAM. suspend_stats just lists the last 2 failed devices, error number and
Dfreezing-of-tasks.txt179 (https://lists.linux-foundation.org/pipermail/linux-pm/2007-May/012309.html).
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DOverview.txt143 as well as mailing lists that can be found from the same site.
/linux-4.4.14/Documentation/PCI/
DPCIEBUS-HOWTO.txt161 allowed to run simultaneously, below lists a few of possible resource
/linux-4.4.14/Documentation/input/
Dinput-programming.txt100 This adds the button_dev structure to linked lists of the input driver and
/linux-4.4.14/Documentation/sound/alsa/
Dcompress_offload.txt130 The timestamp becomes a multiple field structure. It lists the number
/linux-4.4.14/Documentation/arm/Marvell/
DREADME4 This document lists all the ARM Marvell SoCs that are currently
/linux-4.4.14/Documentation/powerpc/
Dhvcs.txt368 provide lists of easily parsed partner vty data: "partner_vtys" and
563 linuxppc-dev@lists.ozlabs.org
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt415 lists, ensure that you have the latest release of uml_utilities if you
3895 this uml-devel post <http://www.geocrawler.com/lists/3/Source-
3903 <http://www.geocrawler.com/lists/3/SourceForge/597/0/> name="pointed
4053 mailing lists - either the developer list - user-mode-linux-devel at
4054 lists dot sourceforge dot net (subscription info) or the user list -
4055 user-mode-linux-user at lists dot sourceforge do net (subscription
4066 report this on one of the project mailing lists, either the developer
4067 list - user-mode-linux-devel at lists dot sourceforge dot net
4068 (subscription info) or the user list - user-mode-linux-user at lists
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt50 scatter-gather lists.
/linux-4.4.14/Documentation/gpio/
Ddriver.txt270 [1] http://www.spinics.net/lists/linux-omap/msg120425.html

12