From: insafonov@gmail.com (Ivan Safonov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to mark suspicious code?
Date: Fri, 6 Nov 2015 08:45:46 +0700 [thread overview]
Message-ID: <563C064A.1010108@gmail.com> (raw)
In-Reply-To: <563B58FD.3080406@gmail.com>
Hi all!
How can I mark suspicious code, if I can not fix it?
next prev parent reply other threads:[~2015-11-06 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 13:26 How to mark suspicious code? Ivan Safonov
2015-11-06 1:45 ` Ivan Safonov [this message]
2015-11-06 1:58 ` Greg KH
2015-11-06 3:28 ` Ivan Safonov
2015-11-06 5:02 ` Greg KH
2015-11-06 5:39 ` Nicholas Mc Guire
2015-11-06 14:38 ` Ivan Safonov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563C064A.1010108@gmail.com \
--to=insafonov@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.