Lines Matching full:consider

136    process, consider searching again for existing reports about the issue.
138  * If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
241 above steps. Consider this as reference documentation: it's possible to read it
264  * If you never reported an issue to a FLOSS project before you should consider
302 or might not what you want. You thus might want to consider circumventing the
323 those often get rejected or ignored, so consider yourself warned. But it's still
348 If you get flooded with results consider telling your search engine to limit
373 the issue already got reported as outlined in this document and if not consider
397 What qualifies as security issue is left to your judgment. Consider reading
816 proper release with a version number like '5.7'. If that happens, consider
830 consider obtaining the latest mainline kernel via git (see below) or use the
890 the necessary steps already. If you are new to it, consider following one of
932 installed. If it was fixed there already, consider sticking with this version
948     process, consider searching again for existing reports about the issue.*
963     *If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
970 your kernel. If you did so, consider to decode the information from the
1133    boot phase already got discarded. In this case instead consider using
1329 consider asking in other places for advice. For example ask a friend or post
1485 should consider switching to the newer one and forget about the older one:
1499 you find any matches, consider joining the discussion, unless the fix is
1558 reverted to fix the issue quickly). Hence consider to do a proper bisection