Searched refs:bugs (Results 1 – 25 of 261) sorted by relevance
1234567891011
3 Security bugs8 disclosed as quickly as possible. Please report security bugs to the43 for publicly known bugs are released immediately.45 Although our preference is to release fixes for publicly undisclosed bugs61 In other words our only interest is in getting bugs fixed. All other
69 There are known and unknown bugs, features and misfeatures.70 Currently there are following known bugs:73 bugs/errata to list here.
834 if ((ahc->bugs & AHC_CACHETHEN_DIS_BUG) != 0) in ahc_pci_config()837 if ((ahc->bugs & AHC_CACHETHEN_BUG) != 0) in ahc_pci_config()847 if ((ahc->bugs & AHC_PCI_2_1_RETRY_BUG) != 0 in ahc_pci_config()2053 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic785X_setup()2056 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic785X_setup()2071 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic7860_setup()2074 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic7860_setup()2098 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic7870_setup()2176 ahc->bugs |= AHC_TMODE_WIDEODD_BUG; in ahc_aic7880_setup()2179 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic7880_setup()[all …]
843 return ((ahd->bugs & AHD_PKT_BITBUCKET_BUG) != 0);851 return ((ahd->bugs & AHD_PKT_BITBUCKET_BUG) == 0);875 return ((ahd->bugs & AHD_AUTOFLUSH_BUG) != 0);915 return ((ahd->bugs & AHD_REG_SLOW_SETTLE_BUG) != 0);931 return ((ahd->bugs & AHD_EARLY_REQ_BUG) != 0);939 return ((ahd->bugs & AHD_BUSFREEREV_BUG) == 0);963 return ((ahd->bugs & AHD_LQO_ATNO_BUG) != 0);971 return ((ahd->bugs & AHD_BUSFREEREV_BUG) != 0);979 return ((ahd->bugs & AHD_NONPACKFIFO_BUG) != 0);987 return ((ahd->bugs & AHD_SENT_SCB_UPDATE_BUG) != 0);[all …]
40 security-bugs48 reporting-bugs
5 :Original: :doc:`../../../process/security-bugs`
76 p->bugs |= UART_BUG_NOMSR; in au_platform_setup()95 up->bugs |= UART_BUG_NOMSR; in rt288x_setup()
37 Please send feedback to <linux-bugs@chelsio.com>.64 Please send feedback to <linux-bugs@chelsio.com>.87 Please send feedback to <linux-bugs@chelsio.com>.128 Please send feedback to <linux-bugs@chelsio.com>.
6 obj-y += init.o bugs.o core.o regset.o signal.o xstate.o
48 u16 bugs; /* port bugs */ member129 u16 bugs; /* port bugs */ member
3 :Original: :ref:`Documentation/process/security-bugs.rst <securitybugs>`
13 Finding bugs is not always easy. Have a go though. If you can't find it don't29 Using the provided tools with ``git`` makes finding bugs easy provided the bug
3 Report bugs to <linux-kernel@vger.kernel.org>
4 Report bugs to <linux-kernel@vger.kernel.org>
1 Currently known (or at least suspected) bugs in parport:
3 0. Fix the bugs (see BUGS-parport).
12 one submitters code and make him endorse your bugs. To solve this problem, it49 tracking your trees, and to people trying to troubleshoot bugs in your
3 :Original: :doc:`../../../process/security-bugs`
17 Please send feedback to <linux-bugs@chelsio.com>.
5 lkdtm-$(CONFIG_LKDTM) += bugs.o
20 Please send feedback to <linux-bugs@chelsio.com>.
39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to41 to address and they are not instead falling apart due to unplanned bugs
18 Please send feedback to <linux-bugs@chelsio.com>.
18 has not been upstreamed yet. This can reveal bugs at an early stage.
9 * Fix bugs due to code that sleeps in atomic context.