| /linux-4.1.27/net/sunrpc/ |
| D | cache.c | 54 struct cache_head *sunrpc_cache_lookup(struct cache_detail *detail, in sunrpc_cache_lookup() argument
60 head = &detail->hash_table[hash]; in sunrpc_cache_lookup()
62 read_lock(&detail->hash_lock); in sunrpc_cache_lookup()
66 if (detail->match(tmp, key)) { in sunrpc_cache_lookup()
67 if (cache_is_expired(detail, tmp)) in sunrpc_cache_lookup()
71 read_unlock(&detail->hash_lock); in sunrpc_cache_lookup()
75 read_unlock(&detail->hash_lock); in sunrpc_cache_lookup()
78 new = detail->alloc(); in sunrpc_cache_lookup()
86 detail->init(new, key); in sunrpc_cache_lookup()
88 write_lock(&detail->hash_lock); in sunrpc_cache_lookup()
[all …]
|
| /linux-4.1.27/drivers/net/usb/ |
| D | zaurus.c | 153 struct usb_cdc_mdlm_detail_desc *detail = NULL; in blan_mdlm_bind() local
183 if (detail) { in blan_mdlm_bind()
187 detail = (void *) buf; in blan_mdlm_bind()
188 switch (detail->bGuidDescriptorType) { in blan_mdlm_bind()
190 if (detail->bLength != (sizeof *detail + 2)) in blan_mdlm_bind()
194 if (detail->bLength != (sizeof *detail + 3)) in blan_mdlm_bind()
214 if ((detail->bDetailData[1] & ~0x02) != 0x01) { in blan_mdlm_bind()
221 detail->bLength, in blan_mdlm_bind()
222 detail->bDetailData[0], in blan_mdlm_bind()
223 detail->bDetailData[2]); in blan_mdlm_bind()
[all …]
|
| D | cdc_ether.c | 116 struct usb_cdc_mdlm_detail_desc *detail = NULL; in usbnet_generic_cdc_bind() local
289 if (detail) { in usbnet_generic_cdc_bind()
294 detail = (void *)buf; in usbnet_generic_cdc_bind()
296 if (detail->bGuidDescriptorType == 0) { in usbnet_generic_cdc_bind()
297 if (detail->bLength < (sizeof(*detail) + 1)) in usbnet_generic_cdc_bind()
|
| /linux-4.1.27/include/linux/sunrpc/ |
| D | cache.h | 176 sunrpc_cache_lookup(struct cache_detail *detail,
179 sunrpc_cache_update(struct cache_detail *detail,
183 sunrpc_cache_pipe_upcall(struct cache_detail *detail, struct cache_head *h);
203 static inline int cache_is_expired(struct cache_detail *detail, struct cache_head *h) in cache_is_expired() argument
206 (detail->flush_time > h->last_refresh); in cache_is_expired()
209 extern int cache_check(struct cache_detail *detail,
212 extern void cache_purge(struct cache_detail *detail);
|
| /linux-4.1.27/drivers/mmc/host/ |
| D | toshsd.c | 295 u32 int_reg, int_mask, int_status, detail; in toshsd_irq() local
332 detail = ioread32(host->ioaddr + SD_ERRORSTATUS0); in toshsd_irq()
334 detail & SD_ERR0_RESP_CMD_ERR ? "RESP_CMD " : "", in toshsd_irq()
335 detail & SD_ERR0_RESP_NON_CMD12_END_BIT_ERR ? "RESP_END_BIT " : "", in toshsd_irq()
336 detail & SD_ERR0_RESP_CMD12_END_BIT_ERR ? "RESP_END_BIT " : "", in toshsd_irq()
337 detail & SD_ERR0_READ_DATA_END_BIT_ERR ? "READ_DATA_END_BIT " : "", in toshsd_irq()
338 detail & SD_ERR0_WRITE_CRC_STATUS_END_BIT_ERR ? "WRITE_CMD_END_BIT " : "", in toshsd_irq()
339 detail & SD_ERR0_RESP_NON_CMD12_CRC_ERR ? "RESP_CRC " : "", in toshsd_irq()
340 detail & SD_ERR0_RESP_CMD12_CRC_ERR ? "RESP_CRC " : "", in toshsd_irq()
341 detail & SD_ERR0_READ_DATA_CRC_ERR ? "READ_DATA_CRC " : "", in toshsd_irq()
[all …]
|
| /linux-4.1.27/tools/testing/selftests/powerpc/ |
| D | subunit.h | 14 static inline void test_failure_detail(char *name, char *detail) in test_failure_detail() argument
16 printf("failure: %s [%s]\n", name, detail); in test_failure_detail()
|
| /linux-4.1.27/drivers/edac/ |
| D | edac_mc.c | 985 const char *detail, in edac_ce_error() argument
1003 location, detail, other_detail); in edac_ce_error()
1008 location, detail); in edac_ce_error()
1039 const char *detail, in edac_ue_error() argument
1053 location, detail, other_detail); in edac_ue_error()
1058 location, detail); in edac_ue_error()
1064 msg, msg_aux, label, location, detail, other_detail); in edac_ue_error()
1067 msg, msg_aux, label, location, detail); in edac_ue_error()
1089 char detail[80]; in edac_raw_mc_handle_error() local
1094 snprintf(detail, sizeof(detail), in edac_raw_mc_handle_error()
[all …]
|
| D | i5100_edac.c | 444 char detail[80]; in i5100_handle_ce() local
447 snprintf(detail, sizeof(detail), in i5100_handle_ce()
454 msg, detail); in i5100_handle_ce()
466 char detail[80]; in i5100_handle_ue() local
469 snprintf(detail, sizeof(detail), in i5100_handle_ue()
476 msg, detail); in i5100_handle_ue()
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | renesas,rsnd.txt | 16 see below for detail.
19 see below for detail.
22 see below for detail.
25 see below for detail.
|
| /linux-4.1.27/fs/nfsd/ |
| D | nfs4idmap.c | 172 warn_no_idmapd(struct cache_detail *detail, int has_died) in warn_no_idmapd() argument
496 struct ent *key, struct cache_detail *detail, struct ent **item) in idmap_lookup() argument
500 *item = lookup_fn(detail, key); in idmap_lookup()
504 ret = cache_check(detail, &(*item)->h, &rqstp->rq_chandle); in idmap_lookup()
508 *item = lookup_fn(detail, key); in idmap_lookup()
511 cache_put(&(*item)->h, detail); in idmap_lookup()
|
| D | Kconfig | 21 package, available from http://linux-nfs.org/. More detail about
|
| /linux-4.1.27/Documentation/acpi/ |
| D | dsdt-override.txt | 5 When to use this method is described in detail on the
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | arm-versatile.txt | 8 address space. See partition.txt for more detail.
|
| D | atmel-dataflash.txt | 7 address space. See partition.txt for more detail.
|
| D | denali-nand.txt | 11 address space. See partition.txt for more detail.
|
| D | flctl-nand.txt | 18 address space. See partition.txt for more detail.
|
| D | orion-nand.txt | 16 address space. See partition.txt for more detail.
|
| D | hisi504-nand.txt | 25 the address space. See partition.txt for more detail.
|
| D | fsl-upm-nand.txt | 24 detail.
|
| D | gpio-control-nand.txt | 29 address space. See partition.txt for more detail.
|
| D | gpmi-nand.txt | 40 address space. See partition.txt for more detail.
|
| D | davinci-nand.txt | 71 the address space. See partition.txt for more detail. The NAND Flash timing
|
| D | mtd-physmap.txt | 45 address space. See partition.txt for more detail.
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | ssd1289fb.txt | 6 - reg: Should contain address of the controller on the LBC bus. The detail
|
| /linux-4.1.27/Documentation/devicetree/bindings/pci/ |
| D | spear13xx-pcie.txt | 1 SPEAr13XX PCIe DT detail:
|
| /linux-4.1.27/Documentation/devicetree/bindings/watchdog/ |
| D | fsl-imx-wdt.txt | 11 detail please see: Documentation/devicetree/bindings/regmap/regmap.txt.
|
| /linux-4.1.27/lib/ |
| D | lru_cache.c | 653 void (*detail) (struct seq_file *, struct lc_element *)) in lc_seq_dump_details()
668 if (detail) in lc_seq_dump_details()
669 detail(seq, e); in lc_seq_dump_details()
|
| /linux-4.1.27/include/linux/ |
| D | lru_cache.h | 270 void (*detail) (struct seq_file *, struct lc_element *));
|
| /linux-4.1.27/drivers/pci/hotplug/ |
| D | acpiphp_ibm.c | 254 u8 detail = event & 0x0f; in ibm_handle_events() local
264 note->event, detail); in ibm_handle_events()
|
| /linux-4.1.27/Documentation/networking/ |
| D | dctcp.txt | 22 The algorithm is further described in detail in the following two
|
| D | batman-adv.txt | 141 times necessary to see more detail debug messages. This must be
|
| D | lapb-module.txt | 48 be described in detail below. If a callback is not required (!!) then a NULL
|
| D | netdev-FAQ.txt | 212 A: Attention to detail. Re-read your own work as if you were the
|
| D | openvswitch.txt | 65 the following sections go into detail.
|
| D | LICENSE.qlge | 249 be similar in spirit to the present version, but may differ in detail to
|
| D | LICENSE.qlcnic | 249 be similar in spirit to the present version, but may differ in detail to
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | lm77 | 27 This implementation detail implies the following:
|
| D | emc1403 | 48 This implementation detail implies the following:
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 33 For more detail about files under nfsd/ and what they control, see
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | spi-fsl-dspi.txt | 17 detail please see: Documentation/devicetree/bindings/regmap/regmap.txt.
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | omap4_camera.txt | 17 As of Revision AB, the ISS is described in detail in section 8.
|
| D | si476x.txt | 100 | | (see datasheet for more detail)
|
| D | uvcvideo.txt | 31 Both mechanisms complement each other and are described in more detail below.
|
| D | vivid.txt | 38 These features will be described in more detail below.
259 input, one input for each input type. Those are described in more detail
376 HDMI input, one output for each output type. Those are described in more detail
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-probe.txt | 59 Define a probe event (see PROBE SYNTAX for detail).
73 which specifies a range of the source code. (see LINE SYNTAX for detail)
91 pattern, see FILTER PATTERN for detail.
|
| D | perf-script-python.txt | 83 general-purpose scripts to drill down and get more detail about
|
| /linux-4.1.27/Documentation/mtd/ |
| D | spi-nor.txt | 61 drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to fsl-quadspi.c
|
| /linux-4.1.27/Documentation/devicetree/bindings/pwm/ |
| D | pwm-fsl-ftm.txt | 14 Please see ../regmap/regmap.txt for more detail about how to specify endian
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 5.Posting | 8 document will attempt to cover these expectations in reasonable detail;
150 the author of the patch. Tags will be described in more detail below.
173 changed, detail those changes and how other developers should respond. In
192 detail in the SubmittingPatches document; what follows here is a brief
214 detail.
236 be examined in any detail. If there is any doubt at all, mail the patch
|
| D | 8.Conclusion | 14 Various web sites discuss kernel development at all levels of detail. Your
|
| D | 1.Intro | 136 discussed in greater detail later in this document. Consider:
|
| D | 2.Process | 42 detail later on).
|
| /linux-4.1.27/drivers/scsi/ |
| D | dpt_i2o.c | 391 sprintf(pHba->detail, "Adaptec I2O RAID"); in adpt_inquiry()
396 memset(pHba->detail, 0, sizeof(pHba->detail)); in adpt_inquiry()
397 memcpy(&(pHba->detail), "Vendor: Adaptec ", 16); in adpt_inquiry()
398 memcpy(&(pHba->detail[16]), " Model: ", 8); in adpt_inquiry()
399 memcpy(&(pHba->detail[24]), (u8*) &buf[16], 16); in adpt_inquiry()
400 memcpy(&(pHba->detail[40]), " FW: ", 4); in adpt_inquiry()
401 memcpy(&(pHba->detail[44]), (u8*) &buf[32], 4); in adpt_inquiry()
402 pHba->detail[48] = '\0'; /* precautionary */ in adpt_inquiry()
540 return (char *) (pHba->detail); in adpt_info()
565 seq_printf(m, "%s\n", pHba->detail); in adpt_show_info()
|
| D | dpti.h | 218 char detail[55]; member
|
| /linux-4.1.27/Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 7 Qsys system. See more detail in: http://www.alterawiki.com/wiki/Sopc2dts
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 9 'find /sys/ -name 'pcrs''. For the detail information of PPI,
|
| D | sysfs-class-regulator | 58 imply "on", but provide more detail.
|
| /linux-4.1.27/Documentation/leds/ |
| D | leds-lm3556.txt | 51 Please refer datasheet for more detail about N-Blank, Pulse time and N Period.
|
| /linux-4.1.27/Documentation/block/ |
| D | stat.txt | 19 following table, and described in more detail below.
|
| D | queue-sysfs.txt | 4 This text file will detail the queue files that are located in the sysfs tree
|
| D | data-integrity.txt | 96 However, this level of detail is required when preparing the
|
| D | biodoc.txt | 58 2.2 The bio struct in detail (multi-page io unit)
|
| /linux-4.1.27/drivers/net/can/sja1000/ |
| D | Kconfig | 97 http://www.embeddedarm.com/products/board-detail.php?product=TS-CAN1
|
| /linux-4.1.27/Documentation/accounting/ |
| D | delay-accounting.txt | 38 in detail in a separate document in this directory. Taskstats returns a
|
| D | taskstats.txt | 39 explained in more detail below.
|
| /linux-4.1.27/Documentation/w1/masters/ |
| D | ds2490 | 47 detail, but my observation is if fewer bytes are requested than are
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | cpufreq-stats.txt | 32 cpufreq stats provides following statistics (explained in detail below).
|
| /linux-4.1.27/Documentation/vm/ |
| D | page_owner.txt | 51 There is one notice that is caused by implementation detail. page owner
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 35 [ small detail: on "ideal" hardware, at any time all tasks would have the same
89 other HZ detail. Thus the CFS scheduler has no notion of "timeslices" in the
|
| D | sched-bwc.txt | 43 more detail below.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.arcmsr | 50 ** and detail description
|
| D | libsas.txt | 383 All this process is shown in detail in the function do_smp_func()
|
| D | LICENSE.qla4xxx | 250 be similar in spirit to the present version, but may differ in detail to
|
| D | LICENSE.qla2xxx | 251 be similar in spirit to the present version, but may differ in detail to
|
| D | ChangeLog.megaraid_sas | 48 4. Free event detail memory without device ID check.
|
| D | scsi_mid_low_api.txt | 735 In some cases more detail is given in scsi_host.h than below.
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio-rmu.txt | 37 SoC will detail which and how many of these sub-controllers are implemented.
|
| /linux-4.1.27/Documentation/s390/ |
| D | 3270.txt | 73 Here are the installation steps in detail:
130 Here are the testing steps in detail:
|
| D | cds.txt | 25 every detail.This information can be obtained from the ESA/390 Principles of
|
| D | Debugging390.txt | 13 390 IO in any detail. It is intended to complement the documents in the
|
| /linux-4.1.27/Documentation/input/ |
| D | sentelic.txt | 469 section A for packet parsing detail(ignore byte 4, bit ~ 7)
473 section B for packet parsing detail
477 section A for packet parsing detail
481 section A for packet parsing detail (ignore byte 4, bit ~ 7)
|
| /linux-4.1.27/fs/nfs/ |
| D | Kconfig | 17 mount(8) man page. More detail about the Linux NFS client
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | Sound-FAQ | 38 How sound works in detail
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 17 We describe in much greater detail the theory behind the nested VMX feature,
|
| D | timekeeping.txt | 274 avoid repetition of the detail here. It should be pointed out that the APIC
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 154 necessary information for the framework. The struct is also explained in detail
|
| /linux-4.1.27/Documentation/locking/ |
| D | spinlocks.txt | 77 attention to design detail (see Documentation/RCU/listRCU.txt).
|
| D | rt-mutex-design.txt | 80 blocked on one of its locks. This is described in more detail
322 in more detail, but is set whenever there are waiters on a mutex.
|
| /linux-4.1.27/Documentation/laptops/ |
| D | disk-shock-protection.txt | 80 There is a technical detail of this implementation that may cause some
|
| D | thinkpad-acpi.txt | 777 The ThinkPad LED sysfs interface is described in detail by the LED class
|
| /linux-4.1.27/drivers/cpufreq/ |
| D | Kconfig | 44 This will show detail CPU frequency translation table in sysfs file
|
| /linux-4.1.27/fs/cifs/ |
| D | Kconfig | 79 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | nilfs2.txt | 270 For detail on the format of each file, please see include/linux/nilfs2_fs.h.
|
| D | autofs4-mount-control.txt | 100 somewhat more detail to the implementation but it isn't needed for the
101 sake of the problem explanation. The one important detail is that these
|
| D | coda.txt | 189 kernel should be documented in great detail. This is the aim of this
|
| /linux-4.1.27/Documentation/ |
| D | kobject.txt | 16 adding detail as we go. To that end, here are some quick definitions of
39 safely ignore that implementation detail as the kset core code handles
|
| D | sysfs-rules.txt | 84 Everything else is just a kernel driver-core implementation detail
|
| D | SubmittingPatches | 134 about it in technical detail. It's important to describe the change
325 Contact detail and documentation fixes
454 point out some special detail about the sign-off.
|
| D | HOWTO | 104 These files describe in explicit detail how to successfully create
379 already discussed in detail are only recorded at the mailing list
|
| D | kernel-per-CPU-kthreads.txt | 27 echo 1 > max_graph_depth # Increase the "1" for more detail
|
| D | kernel-docs.txt | 334 different types of devices and their properties. Going into detail
|
| /linux-4.1.27/scripts/ |
| D | analyze_suspend.py | 2472 detail = ' var devtable = [];\n'
2475 detail += ' devtable[%d] = "%s";\n' % (data.testnumber, topo)
2476 detail += ' var bounds = [%f,%f];\n' % (t0, tMax)
2479 '<script type="text/javascript">\n'+detail+\
|
| /linux-4.1.27/Documentation/serial/ |
| D | tty.txt | 35 about to enter and exit although this detail matters not).
|
| D | moxa-smartio | 77 Public License announcement in each source code file for more detail.
|
| /linux-4.1.27/Documentation/isdn/ |
| D | INTERFACE | 463 para = protocol and function specific. See isdnif.h for detail.
717 para = protocol and function specific. See isdnif.h for detail.
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | provider.txt | 308 structure pointer as an argument, that will detail which
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 442 detail in vlocks.txt.
|
| /linux-4.1.27/Documentation/trace/ |
| D | events.txt | 295 which can take various forms and are described in detail below;
|
| D | ftrace.txt | 1878 need to see what happens in detail on any areas (or specific
|
| /linux-4.1.27/Documentation/ioctl/ |
| D | cdrom.txt | 586 4-bit value used to control spindown (TODO: more detail here)
|
| /linux-4.1.27/Documentation/crypto/ |
| D | descore-readme.txt | 73 in full gory detail (ALT_ECB is a libdes variant):
|
| /linux-4.1.27/arch/x86/math-emu/ |
| D | README | 128 detail from the way an 80486 does.
|
| /linux-4.1.27/tools/usb/usbip/ |
| D | COPYING | 239 be similar in spirit to the present version, but may differ in detail to
|
| /linux-4.1.27/drivers/staging/rtl8192e/ |
| D | license | 239 similar in spirit to the present version, but may differ in detail to
|
| /linux-4.1.27/kernel/trace/ |
| D | Kconfig | 326 is to be analyzed in much detail.
|
| /linux-4.1.27/drivers/staging/rtl8192u/ |
| D | copying | 239 be similar in spirit to the present version, but may differ in detail to
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-error-recovery.txt | 373 for additional detail on real-life experience of the causes of
|
| /linux-4.1.27/ |
| D | COPYING | 255 be similar in spirit to the present version, but may differ in detail to
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 136 The main requirement that will be defined in more detail below is
141 and properties to be present. This will be described in detail in
514 the storage format. This chapter does _not_ describe the detail of the
|
| /linux-4.1.27/net/ipv4/ |
| D | Kconfig | 521 For more detail see http://www.icir.org/floyd/hstcp.html
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 260 not described in great detail -- one could imagine using process
293 not described in great detail -- one could imagine using process
|
| D | whatisRCU.txt | 192 and is described in more detail in a later section. Instead of
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 984 The sections below describe this in more detail.
1182 forge.net/> and explains these in detail, as well as
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1580 The problem is described in more detail at:
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1533 differ in detail to address new problems or concerns. See
|