linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning from Linus' tree
Date: Fri, 24 Sep 2010 14:32:19 +0200	[thread overview]
Message-ID: <20100924123215.GA5368@nowhere> (raw)
In-Reply-To: <20100924140859.038ccf89.sfr@canb.auug.org.au>

On Fri, Sep 24, 2010 at 02:08:59PM +1000, Stephen Rothwell wrote:
> Hi Arnd,
> 
> Today's (and lots before) linux-next build (i386 defconfig) produced this
> warning:
> 
> fs/autofs4/root.c:31: warning: 'autofs4_root_compat_ioctl' declared 'static' but never defined
> 
> Introduced by commit c9243f5bdd6637b2bb7dc254b54d9edf957ef17e
> ("autofs/autofs4: Move compat_ioctl handling into fs").


Yeah, I've seen two patches:

autofs: only declare function when CONFIG_COMPAT is defined
autofs4: fix compilation warning

I'm going to relay them. Thanks!

  reply	other threads:[~2010-09-24 12:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  4:08 linux-next: build warning from Linus' tree Stephen Rothwell
2010-09-24 12:32 ` Frederic Weisbecker [this message]
2010-10-27  0:00 Stephen Rothwell
2010-10-27  0:29 Stephen Rothwell
2010-10-27  0:58 ` Jesse Gross
2011-06-03  1:00 Stephen Rothwell
2011-06-03  1:10 Stephen Rothwell
2011-06-03 14:17 ` David Sterba
2017-02-26 23:23 Stephen Rothwell
2019-08-29 22:23 Stephen Rothwell
2019-08-29 22:29 ` Thomas Gleixner
2019-08-30  0:25   ` Stephen Rothwell
2021-06-01  7:20 Stephen Rothwell
2021-07-08  2:25 ` Stephen Rothwell
2021-07-20  7:31   ` Stephen Rothwell
2021-08-10  9:29     ` Stephen Rothwell

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=20100924123215.GA5368@nowhere \
    --to=fweisbec@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).