On Thu, Sep 2, 2010 at 11:58 AM, Adam Williamson <awilliam@xxxxxxxxxx> wrote:
Sure, my problem lies not it that fact that there are suspend issues, but in that no attempt was even made to address the suspend issues.
My system suspends and resumes fine on f13 with the 2.6.33 kernels, so it isn't unreasonable to expect this functionality to continue on a stable release.
It is however, perfectly reasonable to expect that having tried a kernel at the request of a fedora developer on fedora-test-list and then having filed a bug against said kernel reporting problems, that someone might actually have a few minutes required to actually ask a few more questions and try and address the problem.
Otherwise, why did they ask for feedback if it was just to be ignored?
Rodd
Because there are always suspend issues, kernel team doesn't considerOn Thu, 2010-09-02 at 11:00 +1000, Rodd Clarkson wrote:
> Hi all,
>
> Why was kernel-2.6.34.x pushed to updates in f13 when three people had
> reported suspend issues with the kernel and no attempt was made to
> address these issues.
>
> see: https://bugzilla.redhat.com/show_bug.cgi?id=615560
>
> I
> Rodd
suspend problems a blocker for release.
Sure, my problem lies not it that fact that there are suspend issues, but in that no attempt was even made to address the suspend issues.
My system suspends and resumes fine on f13 with the 2.6.33 kernels, so it isn't unreasonable to expect this functionality to continue on a stable release.
It is however, perfectly reasonable to expect that having tried a kernel at the request of a fedora developer on fedora-test-list and then having filed a bug against said kernel reporting problems, that someone might actually have a few minutes required to actually ask a few more questions and try and address the problem.
Otherwise, why did they ask for feedback if it was just to be ignored?
Rodd
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
