PRs for tag 'amr'
This is an experimental report containing PRs for tag 'amr' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'amr':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2010/12/20 | kern/153303 | [amr] amr device driver dont detect logical drive amrd0 on srcu42x on 8_0, 8_1 | |
| o | 2007/07/09 | kern/114438 | [amr] Anomalous performance with multiple arrays and amr(4) | |
| o | 2007/05/28 | kern/113098 | [amr] Cannot read from amrd while under heavy load | |
| o | 2006/03/06 | kern/94139 | scottl | [amr] [regression] amr broken with LSILogic MegaRAID Series 428 (HP NetRAID) on 6-STABLE: reading app hangs |
| o | 2004/10/07 | kern/72433 | [amr] [patch] AMR raid, amrreg.h struct amr_enquery3 ae_driveformat should be u_int8_t |
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.