From: Greg KH <gregkh@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
devel@driverdev.osuosl.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <zbr@ioremap.net>
Subject: Re: [PATCH -next] staging/pohmelfs: fix write_inode parameter warning
Date: Sun, 7 Mar 2010 07:50:03 -0800 [thread overview]
Message-ID: <20100307155003.GA1615@suse.de> (raw)
In-Reply-To: <10f740e81003070122y32765942y33c167b5ba4ca8ac@mail.gmail.com>
On Sun, Mar 07, 2010 at 10:22:27AM +0100, Geert Uytterhoeven wrote:
> On Thu, Feb 25, 2010 at 23:41, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > sparse warns that:
>
> Not just sparse, plain gcc as well...
>
> > drivers/staging/pohmelfs/inode.c:1797: warning: initialization from incompatible pointer type
> >
> > so fix pohmelfs_write_inode() to have the expected parameters.
>
> And now it's in mainline, too...
This fix is queued up in the tree already sent to Linus so it should all
be resolved soon.
thanks,
greg k-h
prev parent reply other threads:[~2010-03-07 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 7:35 linux-next: Tree for February 25 Stephen Rothwell
2010-02-25 17:21 ` linux-next: Tree for February 25 (quota) Randy Dunlap
2010-03-01 13:27 ` Jan Kara
2010-03-01 16:56 ` Randy Dunlap
2010-02-25 17:55 ` [PATCH -next] staging: fix wlan-ng printk format warning Randy Dunlap
2010-02-25 17:55 ` [PATCH -next] fs: fix compat_ioctl when CONFIG_BLOCK=n Randy Dunlap
2010-02-25 21:27 ` [PATCH -next] pktcdvd: improve BKL and compat_ioctl.c usage Arnd Bergmann
2010-02-25 22:10 ` Randy Dunlap
2010-03-02 12:06 ` Ingo Molnar
2010-03-02 23:38 ` Stephen Rothwell
2010-02-25 22:41 ` [PATCH -next] staging/pohmelfs: fix write_inode parameter warning Randy Dunlap
2010-02-26 0:41 ` Stephen Rothwell
2010-03-07 9:22 ` Geert Uytterhoeven
2010-03-07 15:50 ` Greg KH [this message]
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=20100307155003.GA1615@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=zbr@ioremap.net \
/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).