(In reply to comment #349)
> (In reply to comment #348)
>
> You need to open a new bug report with a thorough explanation of your test
> case, expected and observed results, and any pertinent data you may have
> collected. Leave a note here referencing your newly created bug but posting
> any
> data here is not going to help anyone. This bug is closed due to a lack of
> focus.
yup.
Guys, problems like this aren't sovled very effectively via bugzilla.
Please prefer to report these issues via email to linux-kernel and
myself and any developers who you think might be relevant. it's confusing,
and clarity is important. Being able to provide a means by which others
can demonstrate the problem is a huge benefit.
(In reply to comment #349)
> (In reply to comment #348)
>
> You need to open a new bug report with a thorough explanation of your test
> case, expected and observed results, and any pertinent data you may have
> collected. Leave a note here referencing your newly created bug but posting
> any
> data here is not going to help anyone. This bug is closed due to a lack of
> focus.
yup.
Guys, problems like this aren't sovled very effectively via bugzilla.
Please prefer to report these issues via email to linux-kernel and
myself and any developers who you think might be relevant. it's confusing,
and clarity is important. Being able to provide a means by which others
can demonstrate the problem is a huge benefit.