Home
last modified time | relevance | path

Searched refs:rc1 (Results 1 – 18 of 18) sorted by relevance

/linux-3.4.99/drivers/ide/
Dqd65xx.c426 int rc1, rc2 = -ENODEV; in qd65xx_init() local
431 rc1 = qd_probe(0x30); in qd65xx_init()
432 if (rc1) in qd65xx_init()
435 if (rc1 < 0 && rc2 < 0) in qd65xx_init()
/linux-3.4.99/Documentation/scsi/
DChangeLog.megaraid_sas4 Current Version : 00.00.06.14-rc1
5 Old Version : 00.00.06.12-rc1
14 Current Version : 00.00.06.12-rc1
15 Old Version : 00.00.05.40-rc1
29 Current Version : 00.00.05.40-rc1
30 Old Version : 00.00.05.38-rc1
37 Current Version : 00.00.05.38-rc1
38 Old Version : 00.00.05.34-rc1
51 Current Version : 00.00.05.34-rc1
52 Old Version : 00.00.05.29-rc1
[all …]
Dlpfc.txt19 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
72 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
DChangeLog.lpfc19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
/linux-3.4.99/Documentation/ja_JP/
DHOWTO276 - 2週間後、-rc1 カーネルがリリースされ、この後にはカーネル全体の安定
279 -rc1 の後で受け付けられることもあることを覚えておいてください。な
281 ない限り、退行のリスクは無いからです。-rc1 がリリースされた後、
/linux-3.4.99/Documentation/ko_KR/
DHOWTO242 - 2주 후에 -rc1 커널이 배포되며 지금부터는 전체 커널의 안정성에 영향을
244 완전히 새로운 드라이버(혹은 파일시스템)는 -rc1 이후에만 받아들여진다는
248 생겨난 버그)를 일으킬 만한 위험을 가지고 있지 않기 때문이다. -rc1
/linux-3.4.99/Documentation/zh_CN/
DHOWTO212 - 两个星期以后-rc1版本内核发布。之后只有不包含可能影响整个内核稳定性的
214 可能在-rc1后被接受是因为这样的修改完全独立,不会影响其他的代码,所以
215 没有造成内核退步的风险。在-rc1以后也可以用git向Linus提交补丁,不过所
/linux-3.4.99/drivers/scsi/ibmvscsi/
Dibmvstgt.c102 long rc, rc1; in send_iu() local
127 rc1 = h_send_crq(vport->dma_dev->unit_address, crq.raw[0], crq.raw[1]); in send_iu()
129 if (rc1) { in send_iu()
130 eprintk("%ld sending response\n", rc1); in send_iu()
131 return rc1; in send_iu()
/linux-3.4.99/drivers/net/ethernet/ibm/
Dibmveth.c754 int rc1 = 0, rc2 = 0; in ibmveth_set_csum_offload() local
820 rc1 = -EIO; in ibmveth_set_csum_offload()
822 rc1 = -EIO; in ibmveth_set_csum_offload()
831 return rc1 ? rc1 : rc2; in ibmveth_set_csum_offload()
/linux-3.4.99/fs/cifs/
Dinode.c690 int rc1 = 0; local
692 rc1 = CIFSGetSrvInodeNumber(xid, pTcon,
697 if (rc1 || !fattr.cf_uniqueid) {
698 cFYI(1, "GetSrvInodeNum rc %d", rc1);
/linux-3.4.99/drivers/s390/net/
Dqeth_core_main.c1540 int rc1 = 0, rc2 = 0, rc3 = 0; in qeth_halt_channels() local
1543 rc1 = qeth_halt_channel(&card->read); in qeth_halt_channels()
1546 if (rc1) in qeth_halt_channels()
1547 return rc1; in qeth_halt_channels()
1555 int rc1 = 0, rc2 = 0, rc3 = 0; in qeth_clear_channels() local
1558 rc1 = qeth_clear_channel(&card->read); in qeth_clear_channels()
1561 if (rc1) in qeth_clear_channels()
1562 return rc1; in qeth_clear_channels()
/linux-3.4.99/Documentation/development-process/
D2.Process48 be called 2.6.40-rc1. The -rc1 release is the signal that the time to
72 January 18 2.6.38-rc1, merge window closes
/linux-3.4.99/Documentation/
DHOWTO239 - After two weeks a -rc1 kernel is released it is now possible to push
242 (or filesystem) might be accepted after -rc1 because there is no
245 is being added. git can be used to send patches to Linus after -rc1
Dmd.txt236 this will be a very large number (or 'none' since 2.6.30-rc1). At
Dkprobes.txt538 As of Linux v2.6.15-rc1, multiple handlers (or multiple instances of
Dkmemcheck.txt46 As of version 2.6.31-rc1, kmemcheck is included in the mainline kernel.
/linux-3.4.99/Documentation/filesystems/
Dext4.txt122 - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-write-2.6.27-rc1.html
123 - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-readwrite-2.6.27-rc1.html
/linux-3.4.99/Documentation/RCU/
DRTFP.txt177 [LinusTorvalds2011Linux2:6:38:rc1:NPigginVFS], an RCU-protected red-black
2343 @unpublished{LinusTorvalds2011Linux2:6:38:rc1:NPigginVFS
2345 ,Title="Linux 2.6.38-rc1"