Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionNilesh Javali (Marvell)
2022-01-25 10:27:46 UTC
[Marvell] Update RHEL drivers to support cnic driver
1. Feature Overview
a. Name of feature:
Misc bug fixes
b. Feature description: Update the driver in rhel8.7 to add misc bug fixes.
2. Feature Details
a. Architectures: Intel / AMD (x86_64)
b. Bugzilla dependencies:
c. Drivers or hardware dependencies, including a specific platform or CPU:
d. Library or other software dependencies:
e. Upstream acceptance information, including Linus's kernel version in which the feature appears and the date on which this feature was accepted or is targeted for acceptance into Linus's kernel:
mkp/scsi.git 5.17/scsi-fixes 5.18/scsi-queue
f. External links: Link to upstream submittal of patches
g. Severity (H,M,L): High
h. Feature required by date (for example, the date on which hardware requiring this feature is planned for launch): Partner provided date at which hardware will be generally available
3. Business Justification
a. Why is this feature needed?
b. What hardware or software does this enable?
c. If hardware, is it on-board in a system (eg, LOM) or an add-on card? Add-on card
d. Business impact?
e. What market problems / audience does it address?
4. QE Test Plan
Steps/procedures that Marvell uses to test so RH can emulate.
5. Primary contact at Red Hat, email, phone (chat)
a. First_Name Last_Name: Mark Russell
b. xxx_xxxx: mrussell
c. Phone Number:
6. Primary contact at Partner, email, phone (chat)
a. First_Name Last_Name: Girish Basrur
b. xxx_xxxx: gbasrur
c. Phone Number:
Comment 2Nilesh Javali (Marvell)
2022-05-11 09:47:29 UTC
[Marvell] Update RHEL drivers to support cnic driver 1. Feature Overview a. Name of feature: Misc bug fixes b. Feature description: Update the driver in rhel8.7 to add misc bug fixes. 2. Feature Details a. Architectures: Intel / AMD (x86_64) b. Bugzilla dependencies: c. Drivers or hardware dependencies, including a specific platform or CPU: d. Library or other software dependencies: e. Upstream acceptance information, including Linus's kernel version in which the feature appears and the date on which this feature was accepted or is targeted for acceptance into Linus's kernel: mkp/scsi.git 5.17/scsi-fixes 5.18/scsi-queue f. External links: Link to upstream submittal of patches g. Severity (H,M,L): High h. Feature required by date (for example, the date on which hardware requiring this feature is planned for launch): Partner provided date at which hardware will be generally available 3. Business Justification a. Why is this feature needed? b. What hardware or software does this enable? c. If hardware, is it on-board in a system (eg, LOM) or an add-on card? Add-on card d. Business impact? e. What market problems / audience does it address? 4. QE Test Plan Steps/procedures that Marvell uses to test so RH can emulate. 5. Primary contact at Red Hat, email, phone (chat) a. First_Name Last_Name: Mark Russell b. xxx_xxxx: mrussell c. Phone Number: 6. Primary contact at Partner, email, phone (chat) a. First_Name Last_Name: Girish Basrur b. xxx_xxxx: gbasrur c. Phone Number: