Received: by 10.223.148.5 with SMTP id 5csp6284935wrq; Wed, 17 Jan 2018 11:44:46 -0800 (PST) X-Google-Smtp-Source: ACJfBotVAAIIqub2adE3Kv1oIvjktgkIW6VTkpIcVfOpP0uIhaxnEuu67jEG2J8+khv+heGctL8n X-Received: by 10.159.229.202 with SMTP id t10mr42836013plq.424.1516218286192; Wed, 17 Jan 2018 11:44:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516218286; cv=none; d=google.com; s=arc-20160816; b=jLK8KUhuAggJc/0YmN5cxrzdS0CS2G3oWbwQkqIuNTj1Sa7B/K8t/IlYDM4c9I64zH zBcSgh+avQazr+YcXoJJKoV71WVAF+5oZ+sNgMWlM7kerOIFP9z1Q7uQdvw+LT9gejV5 4yw6wc5K43nFZELym/z9CsUhcPcH/6tmokRhv+4w1DIdMBzy0HM3KglK96Ih+E+fSp4l owvJKBeqSDL5fvsqQOI6GeVPgzxJyljRuGBs8kt+oakD8Lq4WpDJc6n4n2xDN8LZHKoc BzJ5LSm3ZUBOuUAPpcgXxiSGi1WKSS5yarrRp7ejLpP8i9uBg+GRQbv9PgxqzmJcRJW/ 0cYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=uslbyRQlVBS1fGNATBQT7YgHEYbH4ge/0XxRKU8U/zI=; b=PgExPZ7BFAfFUci52wLMJUw9NZ2RjnQ+ygmAo4AnibYzDr4LzZngqP55RpAABX9oz9 BZBAfziSbm+q1sQ/9jDznvj2oejNT8DZz2QzqpT4dmWHms+StmsAYtb6+QCnujbbShRZ Pi6VIwzTvy+8e7dSxXXF8zlQ2gOQqJesRGDgtKrzM314GAMcvwVc9yPvZiyMkC8NNWVx 2IVumobVhvuZA4Xp6qGzsCqo2WHogYt3Dqn62Nhli+4DHWgQ0viCMwLYZjVhcsHkPpHz Jl6V0DPFAVOQk0hg7mm46UqKsCN6RUArLYrcGN/39zHgWo3kfeiHe2arz6zRiA4/RI7f BydQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=i2bv3/hw; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1si5012160plp.678.2018.01.17.11.44.31; Wed, 17 Jan 2018 11:44:46 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=i2bv3/hw; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752919AbeAQToK (ORCPT + 99 others); Wed, 17 Jan 2018 14:44:10 -0500 Received: from mail-ot0-f193.google.com ([74.125.82.193]:46557 "EHLO mail-ot0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752854AbeAQToI (ORCPT ); Wed, 17 Jan 2018 14:44:08 -0500 Received: by mail-ot0-f193.google.com with SMTP id t35so11233251otd.13 for ; Wed, 17 Jan 2018 11:44:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=uslbyRQlVBS1fGNATBQT7YgHEYbH4ge/0XxRKU8U/zI=; b=i2bv3/hwLCQy9gHgi+BCbd9AGpIp8O6bCEqmS10xZPkiR5SSdvBkY+gINBEreJD146 3P9XADZBS1auMCz9LLx9luDpCcH0Kufx+IQFR5WvbuXroLnLsNZQaTjH4GD69lom/3/M Wm5kZcgwlMMpDm/K3zOwraYgUZ9MpRsDapvKbgXRVl1dAk5ahKvvT7HDjLPtN5pv9ljn Wg5nT7MfVq/p/YNrHKjbqUz15aN0th4yaNEL14n3dK3QPNs1GOb+jWIVwsaMhM70/SQM AGAAFN7FAkugSHkfL21tV05oyGHj+TKFwLCiX1KPWwXEC1vdsM4TIXWPc4Q+K9QvAMFu Rbww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=uslbyRQlVBS1fGNATBQT7YgHEYbH4ge/0XxRKU8U/zI=; b=bKTOjrw2zwDU2kYM7zdCYmRfqCuBcG4swn3HyFGiBoTHxsWjMFzp/Qutreyo5ODMkw e0g9OUuYDw13KxJsBoIMsQhwvjkP2rDaOyNoPeGpkcy4V+5PkSvS4YaSz/eWegqBDQsY jzwxjgJtHclxBYcd6NCMmmmAOeTzgcGYICFTV832tn7ljY7GuH+1EgZ2DAfHh4F4PvoD NjvGzHTKF8y67tJRudqmdhZu7axLc5mJmRBXr+CfG1iKpYUoazRwYywlBArMAbiET6BZ J5RLcIjYDQRcHPZqTS+4fSpNVRsCYPXJgOFS0MljR3mIDprAsD/eYPjHgLQo0xdIQBzn ezTQ== X-Gm-Message-State: AKwxytfkagxN9DDLVYR86iNZXL5ins8dLLQ+U87KHHIQanyCnjWh9TQ0 trnwf9Ekm2bT2ePkM5Jn/RNonkteC6TpGY4+oSc= X-Received: by 10.157.39.229 with SMTP id c92mr1762247otb.212.1516218247984; Wed, 17 Jan 2018 11:44:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.17.89 with HTTP; Wed, 17 Jan 2018 11:44:07 -0800 (PST) In-Reply-To: References: <20180116145720.2348043-1-arnd@arndb.de> <20180117082712.GF2759@phenom.ffwll.local> From: Arnd Bergmann Date: Wed, 17 Jan 2018 20:44:07 +0100 X-Google-Sender-Auth: RDLUufPoGYXA-Ch-4g0NR_s1N9Q Message-ID: Subject: Re: [PATCH] [RESEND] drm/gma500: initialize gma_clock_t structures To: Daniel Vetter Cc: Patrik Jakobsson , David Airlie , dri-devel , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 17, 2018 at 3:55 PM, Daniel Vetter wrote: > On Wed, Jan 17, 2018 at 3:36 PM, Arnd Bergmann wrote: >> On Wed, Jan 17, 2018 at 9:27 AM, Daniel Vetter wrote: >>> On Tue, Jan 16, 2018 at 03:57:10PM +0100, Arnd Bergmann wrote: >>>> The two functions pass a partially initialized structure back to the >>>> caller after a memset() on the destination. >>>> >>>> This is not entirely well-defined, most compilers are sensible enough >>>> to either keep the zero-initialization for the uninitialized members, >>>> but gcc-4.4 does not, and it warns about this: >>>> >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c: In function 'mrst_sdvo_find_best_pll': >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:175: warning: 'clock.vco' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:175: warning: 'clock.dot' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:175: warning: 'clock.p2' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:175: warning: 'clock.m2' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:175: warning: 'clock.m1' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c: In function 'mrst_lvds_find_best_pll': >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.p' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.vco' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.p2' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.m2' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.m1' may be used uninitialized in this function >>>> drivers/gpu/drm/gma500/oaktrail_crtc.c:208: warning: 'clock.n' may be used uninitialized in this function >>>> >>>> This adds an initialization at declaration time to avoid the warning >>>> and make it well-defined on all compiler versions. >>>> >>>> Signed-off-by: Arnd Bergmann >>> >>> Applied to drm-misc-next-fixes for 4.16, thx for your patch. >> >> Thanks! >> >>> Aside: Still don't want commit rights? :-) >> >> I think I'm fine without. While I do tend to have a backlog on DRM >> patches that I'd >> like to get merged, they are generally of the kind that I should not >> apply myself >> without the maintainer being involved in some form, and then they can commit >> it themselves. > > Commit rights isn't for pushing unreviewed stuff (our scripts will > remind you of that if you try). But you could just volunteer someone > to review the entire pile and then push it, instead of nagging every > single slacking maintainer individually. I understand, but I could also just nag someone to review and apply the patches, right? Or do the committer and reviewer also need to be separate people? Arnd