On Fri, Jun 1, 2018 at 6:33 PM, Stephen Rothwell wrote:
> Hi Darrick,
>
> On Fri, 1 Jun 2018 17:59:48 -0700 "Darrick J. Wong"
> wrote:
>>
>> > + if (!dax_enabled) {
>> > - pr_debug("VFS (%s): error: dax support not enabled\n",
>> > - sb->s_id);
>> > +
Hi Darrick,
On Fri, 1 Jun 2018 17:59:48 -0700 "Darrick J. Wong"
wrote:
>
> > + if (!dax_enabled) {
> > - pr_debug("VFS (%s): error: dax support not enabled\n",
> > - sb->s_id);
> > + pr_debug("%s: error: dax support not enabled\n",
> > +
On Fri, Jun 01, 2018 at 06:58:46PM +1000, Stephen Rothwell wrote:
> Hi Dan,
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> drivers/dax/super.c
>
> between commits:
>
> ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems")
> 80660f20252d ("dax: c
On Fri, Jun 1, 2018 at 1:58 AM, Stephen Rothwell wrote:
> Hi Dan,
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> drivers/dax/super.c
>
> between commits:
>
> ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems")
> 80660f20252d ("dax: change bdev_da
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
drivers/dax/super.c
between commits:
ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems")
80660f20252d ("dax: change bdev_dax_supported() to support boolean returns")
from the xfs tree and commit:
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
fs/xfs/xfs_inode.h
between commit:
f5c54717bf2b ("xfs: remove xfs_zero_range")
from the xfs tree and commit:
6ea4108852e9 ("xfs: prepare xfs_break_layouts() for another layout type")
from the nvdimm tree.
I fixed i
6 matches
Mail list logo
