From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932672Ab2K1X4w (ORCPT ); Wed, 28 Nov 2012 18:56:52 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:60963 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932390Ab2K1X4v (ORCPT ); Wed, 28 Nov 2012 18:56:51 -0500 Date: Wed, 28 Nov 2012 15:56:50 -0800 From: Andrew Morton To: Andy Shevchenko Cc: linux-kernel@vger.kernel.org, Stefani Seibold , Greg Kroah-Hartman Subject: Re: [PATCH, resend] kfifo: initialize fifo accordingly to C99 standard Message-Id: <20121128155650.cd20d6bf.akpm@linux-foundation.org> In-Reply-To: <1353508271-30646-1-git-send-email-andriy.shevchenko@linux.intel.com> References: <1353508271-30646-1-git-send-email-andriy.shevchenko@linux.intel.com> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Nov 2012 16:31:11 +0200 Andy Shevchenko wrote: > When build a kernel with "make W=1" we will get a warning about missing > initializer. It comes from kfifo usage style. The DEFINE_KFIFO macro doesn't > initialize the buf[] field of the fifo structure. So, using C99 style helps in > such case. I see no such warning. When fixing warnings or compilation errors, please always quote the compiler output in the changelog.