Granted this is a low-priority ticket, but it's only a few lines of device-id
codes to recognize. Any chance someone can take a look at this ticket? I'm
currently in the when-new-kernel-released->patch->recompile-kernel cycle...
Thanks!

It's not a question of "priority" per se, but the fact that RHEL bugs
have to have Issue Tracker tickets assigned to them (which this bug
does not have). I'm not going to comment on merits of this policy.
There can me exceptions, so I added the PM request flag. If PM acks
this, I can proceed with the work (e.g. branch, build, test, and post
for review).

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Unfortunately the previous automated notification about the
non-inclusion of this request in Red Hat Enterprise Linux 5.3 used
the wrong text template. It should have read: this request has been
reviewed by Product Management and is not planned for inclusion
in the current minor release of Red Hat Enterprise Linux.
If you would like this request to be reviewed for the next minor
release, ask your support representative to set the next rhel-x.y
flag to "?" or raise an exception.

This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore is being closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide a sufficient business justification
in order to re-open it.

Note

You need to
log in
before you can comment on or make changes to this bug.