public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k•org>
To: YueHaibing <yuehaibing@huawei•com>
Cc: alsa-devel@alsa-project•org, timur@kernel•org,
	Xiubo.Lee@gmail•com, linuxppc-dev@lists•ozlabs.org,
	tiwai@suse•com, lgirdwood@gmail•com, perex@perex•cz,
	nicoleotsuka@gmail•com, broonie@kernel•org, festevam@gmail•com,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH -next] ASoC: fsl_mqs: fix old-style function declaration
Date: Fri, 11 Oct 2019 15:12:43 +0200	[thread overview]
Message-ID: <87mue7ifxw.fsf@igel.home> (raw)
In-Reply-To: <20191011105606.19428-1-yuehaibing@huawei.com> (yuehaibing@huawei.com's message of "Fri, 11 Oct 2019 18:56:06 +0800")

On Okt 11 2019, YueHaibing <yuehaibing@huawei•com> wrote:

> gcc warn about this:
>
> sound/soc/fsl/fsl_mqs.c:146:1: warning:
>  static is not at beginning of declaration [-Wold-style-declaration]

It's not a function, though.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k•org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2019-10-11 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 10:56 [PATCH -next] ASoC: fsl_mqs: fix old-style function declaration YueHaibing
2019-10-11 13:12 ` Andreas Schwab [this message]
2019-10-11 14:02   ` Yuehaibing
2019-10-11 14:35 ` [PATCH v2 -next] ASoC: fsl_mqs: Move static keyword to the front of declarations YueHaibing
2019-10-11 19:01   ` Nicolin Chen
2019-10-14 12:04   ` Applied "ASoC: fsl_mqs: Move static keyword to the front of declarations" to the asoc tree Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mue7ifxw.fsf@igel.home \
    --to=schwab@linux-m68k$(echo .)org \
    --cc=Xiubo.Lee@gmail$(echo .)com \
    --cc=alsa-devel@alsa-project$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=festevam@gmail$(echo .)com \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=nicoleotsuka@gmail$(echo .)com \
    --cc=perex@perex$(echo .)cz \
    --cc=timur@kernel$(echo .)org \
    --cc=tiwai@suse$(echo .)com \
    --cc=yuehaibing@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox