From: Bob Peterson <rpeterso@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 24 (build failure due to 'GFS2: Allocate reservation during splice_write')
Date: Tue, 24 Feb 2015 11:56:31 -0500 (EST) [thread overview]
Message-ID: <920599110.18428494.1424796991441.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150224051950.GA20733@roeck-us.net>
----- Original Message -----
> On Tue, Feb 24, 2015 at 02:02:57PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150223:
> >
> > The hid tree gained a conflict against Linus' tree.
> >
> > The drm-misc tree gained a build failure for which I applied a merge
> > fix patch.
> >
> > Non-merge commits (relative to Linus' tree): 1108
> > 718 files changed, 18557 insertions(+), 17357 deletions(-)
> >
> > ----------------------------------------------------------------------------
> >
>
> Building powerpc:ppc6xx_defconfig ... failed
> --------------
> Error log:
> fs/gfs2/file.c:1126:18: error: 'gfs2_file_splice_write' undeclared here (not
> in a function)
> .splice_write = gfs2_file_splice_write,
> ^
> make[2]: *** [fs/gfs2/file.o] Error 1
Hi Guenter,
Due to other errors, I rebased the linux-gfs2 tree and pushed a new patch to fix
this problem. Sorry about that.
Regards,
Bob Peterson
prev parent reply other threads:[~2015-02-24 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 3:02 linux-next: Tree for Feb 24 Stephen Rothwell
2015-02-24 5:19 ` linux-next: Tree for Feb 24 (build failure due to 'GFS2: Allocate reservation during splice_write') Guenter Roeck
2015-02-24 16:56 ` Bob Peterson [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=920599110.18428494.1424796991441.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--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