Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932270AbbESJN2 (ORCPT ); Tue, 19 May 2015 05:13:28 -0400 Received: from mail-oi0-f52.google.com ([209.85.218.52]:36387 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932227AbbESJNW (ORCPT ); Tue, 19 May 2015 05:13:22 -0400 MIME-Version: 1.0 In-Reply-To: <1432015882-8646-4-git-send-email-hongzhou.yang@mediatek.com> References: <1432015882-8646-1-git-send-email-hongzhou.yang@mediatek.com> <1432015882-8646-4-git-send-email-hongzhou.yang@mediatek.com> Date: Tue, 19 May 2015 11:13:21 +0200 Message-ID: Subject: Re: [PATCH v2 03/11] pinctrl: mediatek: data struct optimize and remove unused member From: Linus Walleij To: Hongzhou Yang Cc: Rob Herring , Matthias Brugger , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Samuel Ortiz , Lee Jones , Sascha Hauer , Yingjoe Chen , Chaotian Jing , Fabian Frederick , Maoguang Meng , Axel Lin , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-mediatek@lists.infradead.org, "linux-gpio@vger.kernel.org" , srv_heupstream@mediatek.com, Sascha Hauer , dandan.he@mediatek.com, huang eddie Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 813 Lines: 24 On Tue, May 19, 2015 at 8:11 AM, Hongzhou Yang wrote: > From: Yingjoe Chen > > struct mtk_desc_pin.chip, mtk_pinctrl_devdata.invser_offset > and mtk_pinctrl_devdata.chip_type are never used in code. > Remove them. > > Some per-pin data are using int for pin number and offsets. > Change to short and rearrange to reduce const data size. > > Signed-off-by: Yingjoe Chen > Signed-off-by: Hongzhou Yang Applied this version instead. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/