Home
last modified time | relevance | path

Searched refs:plan (Results 1 – 63 of 63) sorted by relevance

/linux-4.1.27/drivers/parport/
DKconfig99 called parport_ip32. If in doubt, saying N is the safe plan.
108 called parport_amiga. If in doubt, saying N is the safe plan.
117 parport_mfc3. If in doubt, saying N is the safe plan.
126 called parport_atari. If in doubt, saying N is the safe plan.
/linux-4.1.27/net/mac802154/
DKconfig18 If you plan to use HardMAC IEEE 802.15.4 devices, you can
/linux-4.1.27/drivers/block/drbd/
Ddrbd_worker.c509 struct fifo_buffer *plan; in drbd_rs_controller() local
512 plan = rcu_dereference(device->rs_plan_s); in drbd_rs_controller()
514 steps = plan->size; /* (dc->c_plan_ahead * 10 * SLEEP_TIME) / HZ; */ in drbd_rs_controller()
523 correction = want - device->rs_in_flight - plan->total; in drbd_rs_controller()
527 fifo_add_val(plan, cps); in drbd_rs_controller()
528 plan->total += cps * steps; in drbd_rs_controller()
531 curr_corr = fifo_push(plan, 0); in drbd_rs_controller()
532 plan->total -= curr_corr; in drbd_rs_controller()
1596 struct fifo_buffer *plan; in drbd_rs_controller_reset() local
1610 plan = rcu_dereference(device->rs_plan_s); in drbd_rs_controller_reset()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/net/
Ddavinci-mdio.txt15 Future plan is to migrate hwmod data base contents into device tree
Dcpsw.txt41 Future plan is to migrate hwmod data base contents into device tree
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-omap.txt19 Future plan is to migrate hwmod data base contents into device tree
/linux-4.1.27/net/wimax/
DKconfig15 for a service plan with a provider.
/linux-4.1.27/drivers/net/slip/
DKconfig23 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
53 you plan to use SLiRP, the SLIP emulator (available from
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dc_can.txt23 Future plan is to migrate hwmod data base contents into device tree
/linux-4.1.27/arch/metag/
DKconfig182 If you plan on running programs which are compiled to use hard floats
192 If you plan on running DSP programs say Y here.
211 Say Y if you plan to use a DA debug adapter with Linux. The presence
/linux-4.1.27/drivers/net/ethernet/toshiba/
DKconfig38 If you have the wireless-less model of PS3 or have no plan to
/linux-4.1.27/Documentation/dvb/
Dreadme.txt16 We plan to split this into separate packages, but it's not
/linux-4.1.27/drivers/media/usb/pvrusb2/
DKconfig61 You do not need to select this option unless you plan
/linux-4.1.27/include/linux/
Disdnif.h233 unsigned char plan; /* Numbering plan */ member
/linux-4.1.27/Documentation/security/
Dtomoyo.txt45 --- What is future plan? ---
DSmack.txt596 If you don't know what CIPSO is and don't plan to use it, you can just do :
/linux-4.1.27/drivers/isdn/sc/
Dinterrupt.c130 setup.plan = 0; in interrupt_handler()
/linux-4.1.27/Documentation/scsi/
Dg_NCR5380.txt40 the driver (the raw 5380 driver does not and I don't plan to fiddle with
/linux-4.1.27/drivers/isdn/pcbit/
Dcallbacks.c163 ictl.parm.setup.plan = 0; in cb_in_1()
/linux-4.1.27/drivers/staging/lustre/
DREADME.txt71 if you plan to reexport Lustre filesystem from this client via
/linux-4.1.27/arch/c6x/
DKconfig82 Say Y if you plan on running a kernel in big-endian mode.
/linux-4.1.27/arch/m68k/
DKconfig.machine11 you plan to use this kernel on an Amiga, say Y here and browse the
20 computers (including the TT, Falcon and Medusa). If you plan to use
92 experimental. If you plan to try to use the kernel on such a machine
/linux-4.1.27/drivers/input/serio/
DKconfig47 Say Y here if you plan to use an input device (mouse, joystick,
148 driver, and the new HIL driver is experimental, so if you plan
/linux-4.1.27/Documentation/fmc/
DFMC-and-SDB.txt81 plan to submit it upstream in the future, and don't want to force
Didentifiers.txt61 specifying power consumption or such stuff, but I plan to add it as
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt61 * Have a plan for extending ioctls with new flags or new fields at the end of
69 and reject the ioctl if that's not the case. Otherwise your nice plan for
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-class-ubi16 format. Currently it is 1, and there is no plan to change this.
/linux-4.1.27/drivers/isdn/isdnloop/
Disdnloop.c143 cmd->parm.setup.plan = 0; in isdnloop_parse_setup()
225 cmd.parm.setup.plan = 0; in isdnloop_parse_status()
/linux-4.1.27/drivers/isdn/gigaset/
Di4l.c469 response.parm.setup.plan = 0; in gigaset_isdn_icall()
/linux-4.1.27/Documentation/hwmon/
Dw83627ehf119 The attributes can be written to, which is useful if you plan to
/linux-4.1.27/Documentation/isdn/
DREADME.hysdn74 If you plan to use the capidrv-link to isdn4linux, make sure to load
DREADME.gigaset274 be a public network number according to the local dialing plan, without
DINTERFACE515 para.setup.plan = octet 3 from Calling party number Information Element.
DREADME268 octet 3 of calling party number IE (Numbering plan)
/linux-4.1.27/drivers/isdn/icn/
Dicn.c531 cmd.parm.setup.plan = 0; in icn_parse_status()
539 cmd.parm.setup.plan = 0; in icn_parse_status()
/linux-4.1.27/Documentation/usb/
Dgadget_printer.txt47 BEFORE RELEASING A PRODUCT. If you plan to release a product and don't
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt103 attribute however: the system will not try to plan events beyond the time
/linux-4.1.27/drivers/video/fbdev/
DKconfig251 Say N unless you have such a graphics board or plan to get one
348 If you plan to use the LCD display with your SA-1100 system, say
949 Say Y here if you have a PowerVR 2 card in your box. If you plan to
1119 and 815 chipsets. Say Y if you have and plan to use such a board.
1184 Say Y if you have and plan to use such a board.
2347 far only synchronous displays are supported. If you plan to use
/linux-4.1.27/Documentation/filesystems/
Dgfs2-glocks.txt77 There is a plan to try and remove the go_lock and go_unlock callbacks
Dvfat.txt206 If you plan to make any modifications to the vfat filesystem, please
Drelay.txt314 default mode suits your needs, and you plan to use the read()
/linux-4.1.27/drivers/dma/
DKconfig152 If you plan to use the Image Processing unit in the i.MX3x, say
/linux-4.1.27/Documentation/
Drpmsg.txt292 The plan is also to add static creation of rpmsg channels via the virtio
DHOWTO28 you plan to do low-level development for that architecture. Though they
/linux-4.1.27/scripts/
Dspelling.txt679 paln||plan
/linux-4.1.27/drivers/isdn/act2000/
Dcapi.c710 cmd.parm.setup.plan = msg->msg.connect_ind.addr.tnp; in actcapi_dispatch()
/linux-4.1.27/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt204 Finally, the plan to use M64 windows for SR-IOV, which will be described
/linux-4.1.27/drivers/isdn/hisax/
Dl3ni1.c1575 pc->para.setup.plan = p[2]; in l3ni1_setup()
1585 pc->para.setup.plan = 0; in l3ni1_setup()
Dl3dss1.c1721 pc->para.setup.plan = p[2]; in l3dss1_setup()
1731 pc->para.setup.plan = 0; in l3dss1_setup()
Dcallc.c233 ic.parm.setup.plan = 0; in lli_leased_in()
/linux-4.1.27/kernel/trace/
DKconfig432 This option is required if you plan to use perf-probe subcommand
/linux-4.1.27/arch/arm64/
DKconfig487 Say Y if you plan on running a kernel in big-endian mode.
/linux-4.1.27/Documentation/RCU/
Dchecklist.txt411 memory barriers. You should therefore plan for the CPU
/linux-4.1.27/arch/arm/mm/
DKconfig702 Say Y if you plan on running a kernel in big-endian mode.
/linux-4.1.27/lib/
DKconfig.debug129 Say Y here only if you plan to debug the kernel.
238 you really need it, and what the merge plan to the mainline kernel for
/linux-4.1.27/drivers/isdn/capi/
Dcapidrv.c1097 cmd.parm.setup.plan = cmsg->CallingPartyNumber[1]; in handle_incoming_call()
/linux-4.1.27/drivers/staging/comedi/
DKconfig1254 You should enable compilation this driver if you plan to use a board
/linux-4.1.27/scripts/genksyms/
Dparse.tab.c_shipped885 in Bison 2.4.2's NEWS entry, where a plan to phase it out is
/linux-4.1.27/scripts/kconfig/
Dzconf.tab.c_shipped813 in Bison 2.4.2's NEWS entry, where a plan to phase it out is
/linux-4.1.27/scripts/dtc/
Ddtc-parser.tab.c_shipped745 in Bison 2.4.2's NEWS entry, where a plan to phase it out is
/linux-4.1.27/drivers/isdn/i4l/
Disdn_tty.c2000 info->emu.mdmreg[REG_PLAN] = setup->plan; in isdn_tty_find_icall()
/linux-4.1.27/arch/mips/
DKconfig2622 If you plan to use kernel for capturing the crash dump change
/linux-4.1.27/arch/x86/
DKconfig1810 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux