Bug 245631

Marcus, any reason why you aren't using bug 233500 for this? What's the
difference? I don't see patches attached to either bugzilla... thanks!

Created attachment 158005 [details]
Patch for issues described in this BZ.

Andrius:

It has been difficult for me to consolidate everything for one BZ. Most of these issues
are consolidated, but putting all QLogic work for 4.6 under one BZ has hindered progress.
These patches for this BZ have been available for 2 months and should have been submitted
right away.

Marcus - this bug is currently *not on any list*, and considered a *new
request*. Is bug 233500 different from this bug? The reason I ask is that
feature submissions were due (bugzillas created) by 31-Mar-07, which bug 233500
satisfies.

What are your intentions for use of this bug and bug 233500 for updating qla2xxx?

Andrius:

This is a patch to satisfy 233500. It is one of several. I tried to make 233500 depend on this bug.
My intention is to create 2 -3 more bugs which 233500 will depend on.

Using 233500 to represent all QLogic FC work in 4.6 is an "all eggs in one basket approach".
It doesn't allow for progress on one group of patches while another is being held up for
review etc. So my intention is to submit BZ's to track the work to satisfy 233500.

I made this choice after several discussions with the kernel maintainers for both 5.1 and 4.6.

Sorry if this is more difficult at your end. I just haven't been able to herd everything together
at once. It has really slowed my progress.

Marcus - as long as you have buy-in from RH engineering, that's fine with me.
Please provide an appropriate summary this this patch in bugzilla.

I'm assuming all bugzillas are pieces that will ultimately bump the version to
8.01.07.04?

committed in stream U6 build 55.26. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/

A fix for this issue should have been included in the packages contained in the
RHEL4.6 Beta released on RHN (also available at partners.redhat.com).  

Requested action: Please verify that your issue is fixed to ensure that it is
included in this update release.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to FAILS_QA.

If you cannot access bugzilla, please reply with a message to Issue Tracker and
I will change the status for you.  If you need assistance accessing
ftp://partners.redhat.com, please contact your Partner Manager.

A fix for this issue should have been included in the packages contained in 
the RHEL4.6-Snapshot1 on partners.redhat.com.  

Requested action: Please verify that your issue is fixed to ensure that it is 
included in this update release.

After you (Red Hat Partner) have verified that this issue has been addressed, 
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent 
symptoms of the problem you are having and change the status of the bug to 
FAILS_QA.

If you cannot access bugzilla, please reply with a message about your test 
results to Issue Tracker.  If you need assistance accessing 
ftp://partners.redhat.com, please contact your Partner Manager.

A fix for this issue should be included in RHEL4.6-Snapshot2--available soon on
partners.redhat.com.  

Please verify that your issue is fixed to ensure that it is included in this
update release.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to FAILS_QA.

If you cannot access bugzilla, please reply with a message about your test
results to Issue Tracker.  If you need assistance accessing
ftp://partners.redhat.com, please contact your Partner Manager.

A fix for this issue should have been included in the packages contained in the
RHEL4.6-Snapshot3 on partners.redhat.com.  

Please verify that your issue is fixed to ensure that it is included in this
update release.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to FAILS_QA.

If you cannot access bugzilla, please reply with a message about your test
results to Issue Tracker.  If you need assistance accessing
ftp://partners.redhat.com, please contact your Partner Manager.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0791.html