| /linux-3.4.99/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 91 | ACCESS | REQ | | Section 18.1 |
92 NS | BACKCHANNEL_CTL | REQ | | Section 18.33 |
93 I | BIND_CONN_TO_SESSION | REQ | | Section 18.34 |
94 | CLOSE | REQ | | Section 18.2 |
95 | COMMIT | REQ | | Section 18.3 |
96 | CREATE | REQ | | Section 18.4 |
97 I | CREATE_SESSION | REQ | | Section 18.36 |
98 NS*| DELEGPURGE | OPT | FDELG (REQ) | Section 18.5 |
99 | DELEGRETURN | OPT | FDELG, | Section 18.6 |
102 NS | DESTROY_CLIENTID | REQ | | Section 18.50 |
[all …]
|
| /linux-3.4.99/arch/alpha/lib/ |
| D | ev6-copy_user.S | 76 addq $6,1,$6 # .. .. E .. : Section 3.8 in the CWG
85 addq $7,1,$7 # .. .. E .. : Section 3.8 in the CWG
128 addq $6,1,$6 # .. .. E .. : as the store (Section 3.8 in CWG)
215 addq $6,1,$6 # .. .. E .. : as the store (Section 3.8 in CWG)
|
| /linux-3.4.99/Documentation/networking/ |
| D | multiqueue.txt | 5 Section 1: Base driver requirements for implementing multiqueue support
12 Section 1: Base driver requirements for implementing multiqueue support
28 Section 2: Qdisc support for multiqueue devices
48 Section 3: Brief howto using MULTIQ for multiqueue devices
|
| D | LICENSE.qlcnic | 102 distribute such modifications or work under the terms of Section 1
145 under Section 2) in object code or executable form under the terms of
|
| D | LICENSE.qlge | 102 distribute such modifications or work under the terms of Section 1
145 under Section 2) in object code or executable form under the terms of
|
| /linux-3.4.99/Documentation/input/ |
| D | appletouch.txt | 34 Section "InputDevice"
56 Section "ServerLayout"
|
| /linux-3.4.99/Documentation/dvb/ |
| D | ttusb-dec.txt | 14 Section Filters
|
| /linux-3.4.99/Documentation/development-process/ |
| D | 1.Intro | 23 Section 2 introduces the development process, the kernel release cycle, and
30 Section 3 covers early-stage project planning, with an emphasis on
33 Section 4 is about the coding process; several pitfalls which have been
38 Section 5 talks about the process of posting patches for review. To be
44 Section 6 covers what happens after posting patches; the job is far from
50 Section 7 introduces a couple of "advanced" topics: managing patches with
53 Section 8 concludes the document with pointers to sources for more
|
| /linux-3.4.99/Documentation/fb/ |
| D | sa1100fb.txt | 19 documented in the SA-1100 Developer's Manual, Section 11.7. Dual-panel
|
| D | sh7760fb.txt | 49 Suggest you take a closer look at the SH7760 Manual, Section 30.
|
| /linux-3.4.99/drivers/staging/bcm/ |
| D | Bcmchar.c | 1426 …apter, DBG_TYPE_OTHERS, OSAL_DBG, DBG_LVL_ALL, "\nsFlash2xRead.Section :%x", sFlash2xRead.Section); in bcm_char_ioctl()
1468 …Status = BcmFlash2xBulkRead(Adapter, (PUINT)pReadBuff, sFlash2xRead.Section, ReadOffset, ReadBytes… in bcm_char_ioctl()
1521 …pter, DBG_TYPE_OTHERS, OSAL_DBG, DBG_LVL_ALL, "\nsFlash2xRead.Section :%x", sFlash2xWrite.Section); in bcm_char_ioctl()
1526 …if ((sFlash2xWrite.Section != VSA0) && (sFlash2xWrite.Section != VSA1) && (sFlash2xWrite.Section !… in bcm_char_ioctl()
1568 BcmFlash2xCorruptSig(Adapter, sFlash2xWrite.Section); in bcm_char_ioctl()
1580 …Status = BcmFlash2xBulkWrite(Adapter, (PUINT)pWriteBuff, sFlash2xWrite.Section, WriteOffset, Write… in bcm_char_ioctl()
1598 BcmFlash2xWriteSig(Adapter, sFlash2xWrite.Section); in bcm_char_ioctl()
|
| D | nvm.c | 20 static INT IsSectionWritable(PMINI_ADAPTER Adapter, FLASH2X_SECTION_VAL Section);
4404 if(IsSectionExistInFlash(Adapter,psFlash2xReadWrite->Section) != TRUE) in validateFlash2xReadWrite()
4406 …T(Adapter,DBG_TYPE_PRINTK, 0, 0,"Section<%x> does not exixt in Flash",psFlash2xReadWrite->Section); in validateFlash2xReadWrite()
4409 uiSectStartOffset = BcmGetSectionValStartOffset(Adapter,psFlash2xReadWrite->Section); in validateFlash2xReadWrite()
4410 …_RW, DBG_LVL_ALL, "Start offset :%x ,section :%d\n",uiSectStartOffset,psFlash2xReadWrite->Section); in validateFlash2xReadWrite()
4411 if((psFlash2xReadWrite->Section == ISO_IMAGE1) ||(psFlash2xReadWrite->Section == ISO_IMAGE2)) in validateFlash2xReadWrite()
4413 if(psFlash2xReadWrite->Section == ISO_IMAGE1) in validateFlash2xReadWrite()
4422 else if(psFlash2xReadWrite->Section == ISO_IMAGE2) in validateFlash2xReadWrite()
4440 uiSectEndOffset = BcmGetSectionValEndOffset(Adapter,psFlash2xReadWrite->Section); in validateFlash2xReadWrite()
5065 INT IsSectionWritable(PMINI_ADAPTER Adapter, FLASH2X_SECTION_VAL Section) in IsSectionWritable() argument
[all …]
|
| D | Ioctl.h | 268 FLASH2X_SECTION_VAL Section; //which section has to be read/written member
|
| /linux-3.4.99/Documentation/power/ |
| D | runtime_pm.txt | 76 listed at the end of Section 4 may be used for that device within an interrupt
101 the helper functions described in Section 4 for the device until its status
128 fatal error and will refuse to run the helper functions described in Section
150 The helper functions provided by the PM core, described in Section 4, guarantee
231 as described in Section 2), so the helper funtions will not work until
265 Section 8); it may be modified only by the pm_runtime_no_callbacks()
274 Section 9); it may be modified only by the
392 callbacks described in Section 2 for the device
511 majority of the runtime PM helper funtions described in Section 4 will return
535 helper functions described in Section 4. In that case, pm_runtime_resume()
|
| D | pci.txt | 364 Section 1.
402 is handled in one of the ways described in Section 1 and finally converted into
446 legacy PCI suspend routines (see Section 3), in which case the driver's legacy
465 implements legacy PCI suspends routines (Section 3), in which case the legacy
518 callbacks (see Section 3) are implemented by the device's driver, the legacy
528 Section 3), the driver's legacy resume callback is executed and its result is
|
| /linux-3.4.99/Documentation/RCU/ |
| D | whatisRCU.txt | 32 Section 1, though most readers will profit by reading this section at
34 experiment with should focus on Section 2. People who prefer to start
36 understand the RCU implementation should focus on Section 5, then dive
38 focus on Section 6. Section 7 serves as an index to the docbook API
39 documentation, and Section 8 is the traditional answer key.
|
| /linux-3.4.99/arch/x86/boot/ |
| D | header.S | 201 # Section table
|
| /linux-3.4.99/Documentation/ |
| D | memory-hotplug.txt | 73 (see Section 4.).
94 1GiB. The unit of online/offline operation is "one section". (see Section 3.)
|
| D | vgaarbiter.txt | 10 Section 7, Legacy Devices.
|
| /linux-3.4.99/Documentation/scsi/ |
| D | LICENSE.qla2xxx | 104 distribute such modifications or work under the terms of Section 1
147 under Section 2) in object code or executable form under the terms of
|
| D | LICENSE.qla4xxx | 103 distribute such modifications or work under the terms of Section 1
146 under Section 2) in object code or executable form under the terms of
|
| /linux-3.4.99/drivers/staging/usbip/userspace/ |
| D | COPYING | 92 distribute such modifications or work under the terms of Section 1
135 under Section 2) in object code or executable form under the terms of
|
| /linux-3.4.99/drivers/staging/rtl8192u/ |
| D | copying | 92 distribute such modifications or work under the terms of Section 1
135 under Section 2) in object code or executable form under the terms of
|
| /linux-3.4.99/drivers/staging/rtl8192e/ |
| D | license | 95 modifications or work under the terms of Section 1 above, provided that
138 Section 2) in object code or executable form under the terms of Sections
|
| /linux-3.4.99/ |
| D | COPYING | 108 distribute such modifications or work under the terms of Section 1
151 under Section 2) in object code or executable form under the terms of
|