Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Vladimir Kondratiev <vladimir.kondratiev@linux.intel.com>
Subject: RFC: striving for automotive grade certification
To:     linux-kernel@vger.kernel.org
Message-ID: <613bd2e4-4c06-10ef-772d-5cc057728ecb@linux.intel.com>
Date:   Mon, 4 Feb 2019 12:59:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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