From: Greg KH <greg@kroah.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] Staging: pohmelfs: should include fs_struct.h
Date: Thu, 2 Apr 2009 16:32:26 -0700 [thread overview]
Message-ID: <20090402233226.GA18563@kroah.com> (raw)
In-Reply-To: <20090402211754.GA7479@ioremap.net>
On Fri, Apr 03, 2009 at 01:17:54AM +0400, Evgeniy Polyakov wrote:
> Hi Alexander.
>
> On Thu, Apr 02, 2009 at 03:37:10PM +0400, Alexander Beregalov (a.beregalov@gmail.com) wrote:
> > drivers/staging/pohmelfs/path_entry.c: In function
> > 'pohmelfs_construct_path_string':
> > drivers/staging/pohmelfs/path_entry.c:48: error: dereferencing pointer
> > to incomplete type
> > drivers/staging/pohmelfs/path_entry.c:49: error: dereferencing pointer
> > to incomplete type
> > drivers/staging/pohmelfs/path_entry.c:50: error: dereferencing pointer
> > to incomplete type
> > drivers/staging/pohmelfs/path_entry.c: In function 'pohmelfs_path_length':
> > drivers/staging/pohmelfs/path_entry.c:95: error: dereferencing pointer
> > to incomplete type
> > drivers/staging/pohmelfs/path_entry.c:96: error: dereferencing pointer
> > to incomplete type
> > drivers/staging/pohmelfs/path_entry.c:97: error: dereferencing pointer
> > to incomplete type
> >
> > Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
>
> Looks good. Ack.
> Greg please queue it for inclusion.
Will do. Give me a few days to catch up, was away for a week...
thanks,
greg k-h
prev parent reply other threads:[~2009-04-02 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 11:37 [PATCH] Staging: pohmelfs: should include fs_struct.h Alexander Beregalov
2009-04-02 21:17 ` Evgeniy Polyakov
2009-04-02 23:32 ` 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=20090402233226.GA18563@kroah.com \
--to=greg@kroah.com \
--cc=a.beregalov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.