From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755594AbcJUWvH (ORCPT ); Fri, 21 Oct 2016 18:51:07 -0400 Received: from out28-26.mail.aliyun.com ([115.124.28.26]:34568 "EHLO out28-26.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751839AbcJUWvG (ORCPT ); Fri, 21 Oct 2016 18:51:06 -0400 X-Greylist: delayed 326 seconds by postgrey-1.27 at vger.kernel.org; Fri, 21 Oct 2016 18:51:05 EDT X-Alimail-AntiSpam: AC=CONTINUE;BC=0.09872527|-1;FP=0|0|0|0|0|-1|-1|-1;HT=e02c03280;MF=chengang@emindsoft.com.cn;NM=1;PH=DS;RN=4;RT=4;SR=0;TI=SMTPD_---.74s2B7k_1477089932; Message-ID: <580A9C71.5020605@emindsoft.com.cn> Date: Sat, 22 Oct 2016 06:53:37 +0800 From: Chen Gang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Andrew Morton CC: dhowells@redhat.com, linux-kernel@vger.kernel.org, Chen Gang Subject: Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel References: <1475674810-1560-1-git-send-email-chengang@emindsoft.com.cn> <20161020204122.2afc9264b4671add55112fe7@linux-foundation.org> In-Reply-To: <20161020204122.2afc9264b4671add55112fe7@linux-foundation.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/21/16 11:41, Andrew Morton wrote: > On Wed, 5 Oct 2016 21:40:10 +0800 chengang@emindsoft.com.cn wrote: > >> In api itself, kernel does not use it -- it is divided into ac_etime_hi >> and ac_etime_lo. So kernel side only need generate the correct >> ac_etime_hi and ac_etime_lo, but need not know about comp2_t. >> >> At present, kernel use normal u64 type for it, when kernel provdes it to >> outside, kernel can translate it into ac_etime_hi and ac_etime_lo, >> directly, but need not notice about comp2_t, in fact. > > hm. Why is this an improvement? > For me, it will let code a little more understanding, a little simpler, and let the code a little more extendable (when kernel members really needs comp2_t in future, they need not have to treat it as __u32). Only when comp2_t is really used in api header in future, kernel has to know about it, but kernel still can keep original code no touch. So for me, our changing is harmless. Thanks. -- Chen Gang (陈刚) Managing Natural Environments is the Duty of Human Beings.