From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Changman Lee <cm224.lee@samsung.com>
Subject: Re: linux-next: Tree for Dec 26 (f2fs)
Date: Fri, 26 Dec 2014 11:17:15 -0800 [thread overview]
Message-ID: <549DB43B.7050902@infradead.org> (raw)
In-Reply-To: <20141226193009.60d3f62e@canb.auug.org.au>
On 12/26/14 00:30, Stephen Rothwell wrote:
> Hi all,
>
> There will only be intermittent releases of linux-next between now and
> Jan 5.
>
> Changes since 20141221:
>
on x86_64:
when CONFIG_F2FS_STAT_FS is not enabled:
../fs/f2fs/segment.c: In function 'rewrite_data_page':
../fs/f2fs/segment.c:1233:2: error: implicit declaration of function 'stat_inc_inplace_blocks' [-Werror=implicit-function-declaration]
--
~Randy
next prev parent reply other threads:[~2014-12-26 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 8:30 linux-next: Tree for Dec 26 Stephen Rothwell
2014-12-26 19:12 ` linux-next: Tree for Dec 26 (sst-haswell-pcm) Randy Dunlap
2014-12-26 19:17 ` Randy Dunlap [this message]
2014-12-26 20:59 ` linux-next: Tree for Dec 26 (f2fs) Jaegeuk Kim
2014-12-28 22:52 ` Changman Lee
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=549DB43B.7050902@infradead.org \
--to=rdunlap@infradead.org \
--cc=cm224.lee@samsung.com \
--cc=jaegeuk@kernel.org \
--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 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.