| /linux-4.4.14/tools/perf/arch/x86/tests/ |
| D | gen-insn-x86-dat.awk | 23 going = 0
27 going = 1
31 going = 0
35 if (going) {
|
| /linux-4.4.14/drivers/usb/host/ |
| D | u132-hcd.c | 191 int going; member
259 u132->going += 1; in u132_hcd_delete()
265 "2=%p going=%d pdev=%p\n", hcd, u132, u132->going, pdev); in u132_hcd_delete()
481 if (u132->going > 1) { in u132_hcd_monitor_work()
483 , u132->going); in u132_hcd_monitor_work()
486 } else if (u132->going > 0) { in u132_hcd_monitor_work()
497 u132->going = 1; in u132_hcd_monitor_work()
631 if (u132->going > 1) { in u132_hcd_interrupt_recv()
633 , u132->going); in u132_hcd_interrupt_recv()
642 } else if (u132->going > 0) { in u132_hcd_interrupt_recv()
[all …]
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | xenvm-4.2.dts | 19 /* this field is going to be adjusted by the hypervisor */
49 /* this field is going to be adjusted by the hypervisor */
72 /* this field is going to be adjusted by the hypervisor */
74 /* this field is going to be adjusted by the hypervisor */
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-net-mesh | 13 Indicates whether the data traffic going from a
22 Indicates whether the data traffic going through the
39 Indicates whether the data traffic going through the
85 mesh are going to use classic flooding for any
|
| D | sysfs-class-powercap | 16 Here <control type> determines how the power is going to be
|
| D | sysfs-kernel-slab | 126 cache, a cpu going offline, or as the result of forcing an
|
| /linux-4.4.14/Documentation/ |
| D | hsi.txt | 17 commonly prefixed by AC for signals going from the application die to the
18 cellular die and CA for signals going the other way around.
|
| D | mailbox.txt | 6 client (especially) and controller drivers are likely going to be
|
| D | stable_api_nonsense.txt | 36 First off, I'm not going to address _any_ legal issues about closed
40 questions, I'm a programmer and hence, I'm just going to be describing
|
| D | bcache.txt | 145 - Bad performance, or traffic not going to the SSD that you'd expect
161 - Traffic's still going to the spindle/still getting cache misses
301 Counts instances where data was going to be inserted into the cache from a
|
| D | men-chameleon-bus.txt | 87 per MCB device. But this is likely going to change in the future.
|
| D | SubmittingDrivers | 18 also deals with allocating numbers for devices that are not going to
|
| D | padata.txt | 37 is going to use it.
|
| D | ManagementStyle | 72 fairly easy to backtrack. Since you're not going to be able to waste
245 ends up going overboard and hiding the problem, and as they say, "On the
|
| D | bus-virt-phys-mapping.txt | 84 You want the _virtual_ address when you are actually going to access that
|
| D | BUG-HUNTING | 149 Nobody is going to tell you how to fix bugs. Seriously. You need to work it
|
| D | vfio.txt | 38 and DMA. Without going into the details of each of these, DMA is
477 a number of TCE table levels (if a TCE table is going to be big enough and
|
| D | module-signing.txt | 42 The module signing facility is enabled by going to the "Enable Loadable Module
|
| D | crc32.txt | 19 Since it's 33 bits long, bit 32 is always going to be set, so usually the
|
| D | SubmittingPatches | 377 understands what is going on.
651 when, two or three months later, they are going through perhaps
712 If you are going to include a diffstat after the "---" marker, please
|
| D | dynamic-debug-howto.txt | 335 // see whats going on in dyndbg=value processing
|
| D | parport-lowlevel.txt | 125 function to handle ports going away due to a low-level driver
243 ports going away. Registered devices belonging to that driver are NOT
|
| D | workqueue.txt | 365 If kworkers are going crazy (using too much cpu), there are two types
|
| D | cpu-hotplug.txt | 118 If you merely need to avoid cpus going away, you could also use
|
| D | CodingStyle | 593 to worry about the structure suddenly going away from under them just
899 going unused, mark the definition as __maybe_unused rather than wrapping it in
|
| D | assoc_array.txt | 516 proceed rootwards through the tree, going to the parent node, slot N + 1 to
|
| D | pinctrl.txt | 965 when going to sleep, it might imply that the pin is set into something the
1199 operation and going to sleep, moving from the PINCTRL_STATE_DEFAULT to
|
| D | DMA-API.txt | 197 DMA_TO_DEVICE data is going from the memory to the device
|
| D | memory-barriers.txt | 1949 of going to sleep, and the primitives to initiate a wake up imply certain
2202 Under normal operation, memory operation reordering is generally not going to
|
| /linux-4.4.14/drivers/staging/xgifb/ |
| D | TODO | 2 going to be long. So, I'm writing "cleanups" and not the list.
|
| /linux-4.4.14/drivers/i2c/ |
| D | Kconfig | 128 problem with I2C support and want to see more of what is going on.
135 a problem with I2C support and want to see more of what is going
144 a problem with I2C support and want to see more of what is going
|
| /linux-4.4.14/Documentation/power/ |
| D | notifiers.txt | 18 PM_HIBERNATION_PREPARE The system is going to hibernate, tasks will be frozen
28 PM_RESTORE_PREPARE The system is going to restore a hibernation image.
|
| D | userland-swsusp.txt | 13 are going to develop your own suspend/resume utilities.
|
| D | charger-manager.txt | 78 alarm if it is going to go off earlier than Charger Manager so that
|
| D | pci.txt | 173 is going to be put into a low-power state (D1-D3) and is supposed to generate
429 When the system is going into a sleep state in which the contents of memory will
897 - during system restore, when the system is going back to its pre-hibernation
|
| D | swsusp.txt | 346 anything, not even read-only mount, or you are going to lose your
|
| /linux-4.4.14/Documentation/devicetree/bindings/security/tpm/ |
| D | st33zp24-spi.txt | 11 If set, power must be present when the platform is going into sleep/hibernate mode.
|
| D | st33zp24-i2c.txt | 12 If set, power must be present when the platform is going into sleep/hibernate mode.
|
| /linux-4.4.14/arch/arm/mach-prima2/ |
| D | sleep.S | 47 @ the RAM is going to self refresh mode
|
| /linux-4.4.14/Documentation/RCU/ |
| D | 00-INDEX | 26 - List of RCU papers (bibliography) going back to 1980.
|
| D | rcubarrier.txt | 56 the CPUs executing these callbacks are going to be severely
|
| D | trace.txt | 180 this CPU going offline. These orphaned callbacks have been moved
184 CPU due to other CPUs going offline. Note that ci+co-ca+ql is
|
| D | rcu_dereference.txt | 366 In short, rcu_dereference() is -not- optional when you are going to
|
| D | torture.txt | 97 coming and going.
|
| D | stallwarn.txt | 174 reschedule IPI, that the expedited grace period has been going on for
|
| D | checklist.txt | 357 victim CPU from ever going offline.)
|
| D | whatisRCU.txt | 256 If you are going to be fetching multiple fields from the
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-fan.txt | 12 - alarm-gpios: This pin going active indicates something is wrong with
|
| /linux-4.4.14/drivers/pci/ |
| D | Kconfig | 35 problem with PCI support and want to see more of what is going on.
57 when it is going to be assigned to a guest operating system.
|
| /linux-4.4.14/drivers/usb/wusbcore/ |
| D | Kconfig | 38 CBA support and want to see more of what is going on.
|
| /linux-4.4.14/Documentation/networking/ |
| D | ip_dynaddr.txt | 16 going up. So, the *same* (local AND masqueraded) connections requests that
|
| D | xfrm_sync.txt | 21 the events. i.e we are going to set thresholds to say "let me
74 when going from kernel to user space)
|
| D | ieee802154.txt | 79 This layer is going to be extended soon.
|
| D | ltpc.txt | 50 in my atalkd.conf. What is going on here is that I need to fool
|
| D | dl2k.txt | 178 are going to have extensive functions then it is necessary to set extra
|
| D | eql.txt | 108 modems, one-third for three, one-fourth for four, etc... But going
|
| D | decnet.txt | 16 CONFIG_PROC_FS (to see what's going on)
|
| D | z8530drv.txt | 50 (If you're going to compile the driver as a part of the kernel image,
|
| D | ppp_generic.txt | 103 modem commands, and then going through some sort of dialog with the
|
| D | arcnet.txt | 362 If you need only arc0, then the following commands should get you going:
|
| D | rxrpc.txt | 80 (2) provided with a protocol of the type of underlying transport they're going
|
| /linux-4.4.14/arch/metag/kernel/ |
| D | head.S | 9 ! Setup the stack and get going into _metag_start_kernel
|
| /linux-4.4.14/drivers/pps/ |
| D | Kconfig | 30 problem with PPS support and want to see more of what is going on.
|
| /linux-4.4.14/Documentation/fb/ |
| D | cirrusfb.txt | 7 { just a little something to get people going; contributors welcome! }
|
| D | fbcon.txt | 153 Before going on how to attach, detach and unload the framebuffer console, an
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.hz | 31 on SMP and NUMA systems. If you are going to be using NTSC video
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/sunxi/ |
| D | sram.txt | 21 Each SRAM will have SRAM sections that are going to be handled by the
|
| /linux-4.4.14/Documentation/vm/ |
| D | remap_file_pages.txt | 22 emulation creates new VMAs instead of nonlinear mappings. It's going to
|
| D | userfaultfd.txt | 39 different processes without them being aware about what is going on
52 requested features are going to be enabled) will return into
|
| D | active_mm.txt | 27 some amount of time they are not going to be interested in user space,
|
| D | hugetlbpage.txt | 265 If the user applications are going to request huge pages using mmap system
306 applications are going to use only shmat/shmget system calls or mmap with
|
| D | transhuge.txt | 34 miss is going to run faster.
274 if any driver is going to mangle over the page structure of the tail
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | ad525x_dpot.txt | 31 Locate the device in your sysfs tree. This is probably easiest by going into
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 60 explain what is really going on. If you have a technical objection to a
80 going to remember all the details of the code you posted the last time
88 What if you've tried to do everything right and things still aren't going
91 honestly believe that this decision is going against you wrongly, you can
112 being -mm. Patches which affect multiple subsystems can also end up going
|
| D | 7.AdvancedTopics | 170 All types of review, if they lead to better code going into the kernel, are
|
| D | 5.Posting | 69 on the area of your patch and what is going on elsewhere, basing a patch
|
| D | 2.Process | 273 development cycle, approximately 5-10% of the patches going into the
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig | 268 Select this option if the MB93091 CPU board is going to be used with
274 Select this option if the MB93091 CPU board is going to be used
283 Select this option if the MB93493 multimedia chip is going to be
|
| /linux-4.4.14/net/xfrm/ |
| D | Kconfig | 65 They are required if you are going to use IPsec tools ported
|
| /linux-4.4.14/drivers/rapidio/ |
| D | Kconfig | 46 going on.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | jfs.txt | 29 errors=continue Keep going on a filesystem error.
|
| D | directory-locking | 44 The rules above obviously guarantee that all directories that are going to be
125 children", so if we are going to introduce hybrid objects we will need
|
| D | nilfs2.txt | 54 errors=continue Keep going on a filesystem error.
64 checkpoint if no metadata update is going. This mode
|
| D | overlayfs.txt | 175 rightmost one and going left. In the above example lower1 will be the
|
| D | ext4.txt | 225 errors=continue Keep going on a filesystem error.
279 Since a synchronous write operation is going to
|
| D | xfs-delayed-logging-design.txt | 479 transaction. We don't know how big a checkpoint transaction is going to be
481 number of split log vector regions are going to be used. We can track the
506 Further, if we are going to use a static reservation, which bit of the entire
|
| D | ramfs-rootfs-initramfs.txt | 322 5) Al Viro made the decision (quote: "tar is ugly as hell and not going to be
|
| D | ext2.txt | 29 errors=continue Keep going on a filesystem error.
|
| D | path-lookup.txt | 189 like d_inode going NULL underneath us, if the name was unlinked).
|
| D | Locking | 269 Unless the filesystem is going to redirty_page_for_writepage(), unlock the page
|
| D | vfs.txt | 700 dentry_open: *WARNING: probably going away soon, do not use!* This is an
778 Setting this implies you deal with pages going away under you,
|
| D | sharedsubtree.txt | 831 in ->mnt_master->mnt_slave_list and going through ->mnt_slave.
|
| D | coda.txt | 406 Before going on let us elucidate the role of the various fields. The
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 57 3) For a series going though multiple trees, the binding patch should be
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | f71805f | 141 not going below 1 kHz, as the fan tachometers get confused by lower
144 When the DC method is used, Fintek recommends not going below 5 V, which
|
| D | submitting-patches | 93 detection is going to be successful.
|
| D | adm9240 | 139 An alarm is asserted for any voltage going below or above the set limits.
|
| D | w83791d | 109 going forward.
|
| /linux-4.4.14/arch/blackfin/mach-common/ |
| D | interrupt.S | 180 # We are going to dump something out, so make sure we print IPEND properly
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | ev6-copy_user.S | 62 subq $0, 32, $1 # .. E .. .. : Is this going to be a small copy?
|
| /linux-4.4.14/Documentation/ia64/ |
| D | IRQ-redir.txt | 48 - maximal if the CPU is going to be switched off.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 28 This binding is used to configure the IP driver which is going to handle the
|
| /linux-4.4.14/arch/arm/mach-omap2/ |
| D | sram242x.S | 159 cmp r0, #0x1 @ going to half speed?
164 cmp r0, #0x1 @ going to half speed (post branch link)
|
| D | sram243x.S | 159 cmp r0, #0x1 @ going to half speed?
164 cmp r0, #0x1 @ going to half speed (post branch link)
|
| D | Kconfig | 237 going on could result in system crashes;
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-crypt.txt | 41 This is the device that is going to be used as backend and contains the
|
| D | cache-policies.txt | 14 e.g. to start writing back dirty blocks that are going to be evicte
|
| D | dm-raid.txt | 227 understand how your hardware behaves with discards if you are going to
|
| D | cache.txt | 117 account of normal io traffic going to the devices. More work needs
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-power.txt | 29 A suspend event is used to indicate the system going in and out of the
|
| D | tracepoint-analysis.txt | 15 what is going on within the system. There are a large number of methods for
300 To see where within the function pixmanFillsse2 things are going wrong:
|
| D | ftrace.txt | 17 designers of systems to find what is going on inside the kernel.
30 going on in certain parts of the kernel.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README.freeze | 8 Just mailing me "bttv freezes" isn't going to help much. This README
|
| /linux-4.4.14/arch/mn10300/mm/ |
| D | cache-inv-by-tag.S | 151 clr d2 # we're going to clear tag RAM
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 23 4) Any peripherals that are going to be powered down at the same
|
| /linux-4.4.14/Documentation/acpi/ |
| D | gpio-properties.txt | 67 to the GPIO lines it is going to use and provide the GPIO subsystem with a
|
| /linux-4.4.14/arch/powerpc/platforms/pseries/ |
| D | Kconfig | 92 going on. This does not enable debugging in lpar.c, which must
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | README.hm12 | 20 The UV plane is divided into blocks of 16x8 UV values going from left
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 71 kernel tree without going through the obsolete state first.
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | proc-entries.txt | 30 performance, by setting the number of cycles we wait before going idle
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | timestamping.txt | 31 CLOCK_REALTIME (NTP corrections including going backwards),
32 CLOCK_MONOTONIC (NTP corrections but never going backwards),
|
| /linux-4.4.14/Documentation/scsi/ |
| D | 53c700.txt | 51 to drive it off the CPU or bus clock rather than going to the expense
|
| D | ChangeLog.megaraid | 180 going on.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | functionality | 110 this adapter and there's no point in going on. If the check above is
|
| /linux-4.4.14/Documentation/frv/ |
| D | features.txt | 199 The driver can be configured by running make xconfig, and going to:
241 This driver can be configured by running make xconfig, and going to:
|
| D | gdbstub.txt | 70 Set the serial port on the computer that's going to run GDB to the appropriate
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-domains.txt | 36 our CPU is on, starting from its base domain and going up the ->parent chain.
|
| D | completion.txt | 97 the timeout/signal cases from going out of scope. Consider using dynamically
|
| /linux-4.4.14/Documentation/usb/ |
| D | callbacks.txt | 29 * @suspend: Called when the device is going to be suspended.
|
| D | ehci.txt | 193 going to waste more than half the USB 2.0 bandwidth. Delays between the
|
| D | usbmon.txt | 76 redirected to a desirable location. This is preferred, because it is going
|
| D | power-management.txt | 89 its usbfs file open, whether or not any I/O is going on.
301 device is going to be suspended. If the driver returns a
|
| D | usb-serial.txt | 118 iPAQ - disable autosync by going to the Start/Settings/Connections menu
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | si470x.txt | 60 There is also a library libv4l, which can be used. It's going to have a function
|
| D | vivid.txt | 1042 In order to really see what it going on you will need to create two vivid
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 333 scheduling-clock interrupt going in order to support accurate
338 going, even if all CPUs are otherwise idle.
347 or so. On-going work will eliminate the need even for these
|
| /linux-4.4.14/Documentation/dvb/ |
| D | avermedia.txt | 7 Getting the card going
96 Getting the card going
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.modules | 47 -k sb" yourself to get things going. Eventually things may be fixed so
|
| /linux-4.4.14/Documentation/locking/ |
| D | locktorture.txt | 85 coming and going. This parameter is only useful if
|
| D | rt-mutex-design.txt | 587 yet, so we assume we are going to be a waiter. The reason for this is to
589 now, the owner of the mutex can't release the mutex without going into the
|
| /linux-4.4.14/drivers/net/ethernet/dec/tulip/ |
| D | Kconfig | 72 Use PCI shared memory for the NIC registers, rather than going through
|
| /linux-4.4.14/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 12 within a processor subsystem, and there can be more than one line going to a
|
| /linux-4.4.14/drivers/net/can/ |
| D | Kconfig | 173 a problem with CAN support and want to see more of what is going
|
| /linux-4.4.14/Documentation/gpio/ |
| D | drivers-on-gpio.txt | 13 i.e. a LED will turn on/off in response to a GPIO line going high or low
|
| /linux-4.4.14/Documentation/nfc/ |
| D | nfc-hci.txt | 166 - rcv_from_drv() : handle data coming from the chip, going to HCI
167 - xmit_from_hci() : handle data sent by HCI, going to the chip
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | head-mmu-fr451.S | 280 # since the DAMLR regs are not going to change, we can set them now
|
| D | sleep.S | 277 # unlock the icache which was locked before going to sleep
|
| /linux-4.4.14/arch/arm/plat-samsung/ |
| D | Kconfig | 263 going to sleep. The blocks are then checked on resume for any
|
| /linux-4.4.14/Documentation/arm/ |
| D | kernel_user_helpers.txt | 30 of not using these kernel helpers if your compiled code is not going to
|
| D | cluster-pm-race-avoidance.txt | 393 the cluster is not really going to be powered down.
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 174 and only CONFIG_WATCHDOG_NOWAYOUT determines if the feature is going to be
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 172 that is going to be used. The following strings can be used:
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/ |
| D | memx.fuc | 387 // keep going, if we haven't reached the end
|
| /linux-4.4.14/fs/ |
| D | Kconfig.binfmt | 132 going to use shared libraries from Tru64 version 5.0 or later, say N.
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | client.txt | 67 that the 'direction' member will be going away as it duplicates the
|
| D | provider.txt | 18 The request lines actually correspond to physical lines going from the
|
| /linux-4.4.14/arch/powerpc/boot/dts/ |
| D | mpc832x_mds.dts | 21 * you're going by the schematic, the pin is called "P19J-K22".
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-request-key.txt | 61 to prevent the key from going away, and returns the serial number of the key to
|
| D | Smack.txt | 695 will set the Smack label "Rubble" on packets going out from the socket if the
|
| /linux-4.4.14/drivers/md/ |
| D | Kconfig | 260 the ciphers you're going to use in the cryptoapi configuration.
453 You'll need to activate the digests you're going to use in the
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | ppc-pv.txt | 178 Some instructions require more logic to determine what's going on than a load
|
| /linux-4.4.14/Documentation/m68k/ |
| D | README.buddha | 204 the third IDE port are going into data's Nirwana on the
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 139 Welcome to User Mode Linux. It's going to be fun.
987 Once you've decided how you're going to set up the devices, you boot
1030 o You aren't going to use the device for IP networking, so you don't
2494 At this point, you can get things going with 'next', 'step', or
2643 are going to debug. Then you run it from the toplevel directory of
2743 described below in case you're interested in what's going on.
3177 going to concentrate on that. First, I want to see where the fault
3395 admit that I have no idea what's going on. What I will do, though, is
3398 first, and it may be that if I can catch it immediately, what's going
4075 For any diagnosis, you're going to need to build a debugging kernel.
[all …]
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | Kconfig | 131 for IPv6 use this, but connection tracking is going to follow.
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 8 with many of them going unused for the entire lifetime of the process.
|
| /linux-4.4.14/Documentation/virtual/kvm/arm/ |
| D | vgic-mapped-irqs.txt | 58 interface is going to present it to the guest.
|
| /linux-4.4.14/arch/powerpc/platforms/ |
| D | Kconfig | 291 Say Y here if you're going to use hardware that connects to the
|
| /linux-4.4.14/drivers/iommu/ |
| D | Kconfig | 164 bool "Workaround broken graphics drivers (going away soon)"
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 749 * sure we don't have an SCB prefetch going on.
839 * If we re-enter the data phase after going through another
948 * flush process going as we complete the
1407 * we aren't going to touch host memory.
1694 * and await the bus going free. If this is an untagged transaction
|
| D | aic79xx.seq | 1282 * and await the bus going free. If this is an untagged transaction
1638 * If we re-enter the data phase after going through another
|
| /linux-4.4.14/Documentation/sh/ |
| D | new-machine.txt | 101 board (if there are going to be more than one). In order to interoperate
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 223 going to clear out the cache entirely and reinitialise it. It will then
|
| D | netfs-api.txt | 94 However, since it's unlikely that any two netfs's are going to want to define
889 the cache must be informed if the page is going to go away. It's an indication
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | entry.S | 221 oi __SIE_PROG0C+3(%r14),1 # we are going into SIE now
1181 3: # account system time going idle
|
| /linux-4.4.14/arch/sh/lib/ |
| D | memcpy-sh4.S | 395 ! Size is at least 64 bytes, so will be going round the big loop at least once.
|
| /linux-4.4.14/Documentation/input/ |
| D | input.txt | 266 can. Here goes a description of the current state of things, which is going
|
| D | joystick.txt | 58 and install it before going on.
|
| /linux-4.4.14/drivers/base/ |
| D | Kconfig | 199 going on.
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 154 not going to bring me a Nobel prize :-)
400 by going from long to byte first. Actually we can even avoid the table
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 1044 heart that you are going to have to make several runs through the code till you
1045 have a clue whats going on.
1233 Note that GPR14 is a return address but as we are real men we are going to
1296 I am not going to give a course in 390 IO architecture as this would take me
1844 To create this I'm going to do
1940 There is a lot of useful info in here best found by going in and having a look
|
| D | 3270.txt | 187 driver writes terminal output to it, starting at the top line and going
|
| /linux-4.4.14/arch/cris/arch-v10/kernel/ |
| D | entry.S | 94 ;; check for resched if preemptive kernel or if we're going back to user-mode
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 70 future extensions is going right down the gutters since someone will submit
|
| D | ioctl-number.txt | 32 _IOR, or _IOWR is the type of the data going into the kernel or coming
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 444 MUST be able to reject datagrams going to networks that can not provide
491 going out this port MUST use the specified DOI identifier. All CIPSO
|
| /linux-4.4.14/arch/cris/arch-v10/drivers/ |
| D | Kconfig | 450 that access the I2C I/O pins directly instead of going through the
|
| /linux-4.4.14/drivers/net/ |
| D | Kconfig | 14 you want to use under Linux. If you are going to run SLIP or PPP over
|
| /linux-4.4.14/drivers/atm/ |
| D | Kconfig | 85 when going from 8W to 16W bursts.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 438 that disables "cpuset.sched_load_balance" as those tasks aren't going anywhere
535 extra tasks from other busy CPUs to help them before it is going to
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 389 method call notifies the subsystem the parent group is going away, it
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci.txt | 441 it decides the IRQ isn't going to get handled and masks the IRQ (100,000
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | intel-pt.txt | 375 interesting happens, we can stop it and grab a snapshot of what was going on
|
| /linux-4.4.14/drivers/gpio/ |
| D | Kconfig | 288 Say Y here if you're going to use hardware that connects to the
|
| /linux-4.4.14/scripts/genksyms/ |
| D | parse.tab.c_shipped | 1065 | Report that the YYRULE is going to be reduced. |
|
| /linux-4.4.14/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 893 | Report that the YYRULE is going to be reduced. |
|
| /linux-4.4.14/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 1027 | Report that the YYRULE is going to be reduced. |
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 512 kills the thread without going through unmount.
|
| /linux-4.4.14/drivers/tty/serial/ |
| D | Kconfig | 1345 Bypass console output and keep going even if there is no
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 3634 # Here, we zero the ccode and exception byte field since we're going to
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 2066 You may say N here if you are going to load the Acorn FPEmulator
|