From: Vladimir Kondratiev <vladimir.kondratiev@linux.intel.com>
To: linux-kernel@vger.kernel.org
Subject: RFC: striving for automotive grade certification
Date: Mon, 4 Feb 2019 12:59:22 +0200 [thread overview]
Message-ID: <613bd2e4-4c06-10ef-772d-5cc057728ecb@linux.intel.com> (raw)
Hi,
I am looking how can we get kernel certified for life critical
applications, in particular for automotive industry. Mean drive train,
not infotainment.
To begin with, all certification processes are talking about cleaning
compilation warnings at level higher then usual.
Example would be unused parameter in function. This is what I want to
start with. There are lots of warnings triggered in kernel compilation
by -Wunused-parameter, it is perhaps most frequent warning at all.
Technically it is not hard to fix all such warnings by adding
__always_unused when needed. However this will produce huge patch
touching lots of files for kind of nothing. So, before starting this
effort, I want to consult:
- is this (massive cleanup) right direction in general?
- Any ideas better then marking __always_unused?
- what to do in cases where parameter is unused depending on some
pre-processor conditions?
- is it better to do one huge patch or split into pieces?
Thanks, Vladimir
reply other threads:[~2019-02-04 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=613bd2e4-4c06-10ef-772d-5cc057728ecb@linux.intel.com \
--to=vladimir.kondratiev@linux.intel.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox