From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Abhishek Kulkarni <adkulkar@umail.iu.edu>
Subject: linux-next: v9fs tree build warning
Date: Mon, 27 Jul 2009 10:54:40 +1000 [thread overview]
Message-ID: <20090727105440.f1bd9525.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
Hi Eric,
Today's linux-next build (x86_64 allmodconfig) produced this warning:
fs/9p/vfs_inode.c: In function 'v9fs_get_inode':
fs/9p/vfs_inode.c:218: warning: return makes pointer from integer without a cast
Introduced by commit 3cee01293a246cb6e24aef30c37ddd2e2718de9c ("9p: Fix
possible inode leak in v9fs_get_inode").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-07-27 0:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090727105440.f1bd9525.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adkulkar@umail.iu.edu \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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