Hi Jaegeuk,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/f2fs/dir.c
between commit:
59aa5a3aeead ("fscrypto: make filename crypto functions return 0 on success")
from the ext4 tree and commit:
e06f86e61d7a ("f2fs crypto: avoid unneeded memory allocation in
Hi Jaegeuk,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/f2fs/dir.c
between commit:
59aa5a3aeead ("fscrypto: make filename crypto functions return 0 on success")
from the ext4 tree and commit:
e06f86e61d7a ("f2fs crypto: avoid unneeded memory allocation in
On Mon, May 16, 2016 at 03:22:41PM -0700, Jaegeuk Kim wrote:
> > Sorry, I just ran out of time to try to verify that the patch wouldn't
> > break anything, and given that we're going to need to wait for
> > "fscrypto/f2fs: allow fs-specific key prefix for fs encryption" to go
> > upstream.
>
>
On Mon, May 16, 2016 at 03:22:41PM -0700, Jaegeuk Kim wrote:
> > Sorry, I just ran out of time to try to verify that the patch wouldn't
> > break anything, and given that we're going to need to wait for
> > "fscrypto/f2fs: allow fs-specific key prefix for fs encryption" to go
> > upstream.
>
>
On Mon, May 16, 2016 at 05:30:28PM -0400, Theodore Ts'o wrote:
> On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote:
> > Hi Stephen,
> >
> > Thank you for the notice.
> > I've been waiting for a comment about the below patch targeted to v4.7 from
> > Ted.
> > Meanwhile, I intended to
On Mon, May 16, 2016 at 05:30:28PM -0400, Theodore Ts'o wrote:
> On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote:
> > Hi Stephen,
> >
> > Thank you for the notice.
> > I've been waiting for a comment about the below patch targeted to v4.7 from
> > Ted.
> > Meanwhile, I intended to
On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote:
> Hi Stephen,
>
> Thank you for the notice.
> I've been waiting for a comment about the below patch targeted to v4.7 from
> Ted.
> Meanwhile, I intended to prepare -next for that patch in advance.
> Surely, once I get a sense that I
On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote:
> Hi Stephen,
>
> Thank you for the notice.
> I've been waiting for a comment about the below patch targeted to v4.7 from
> Ted.
> Meanwhile, I intended to prepare -next for that patch in advance.
> Surely, once I get a sense that I
Hi Stephen,
Thank you for the notice.
I've been waiting for a comment about the below patch targeted to v4.7 from Ted.
Meanwhile, I intended to prepare -next for that patch in advance.
Surely, once I get a sense that I need to consider v4.8, I'll drop this patch
for -next right away.
Thanks,
On
Hi Stephen,
Thank you for the notice.
I've been waiting for a comment about the below patch targeted to v4.7 from Ted.
Meanwhile, I intended to prepare -next for that patch in advance.
Surely, once I get a sense that I need to consider v4.8, I'll drop this patch
for -next right away.
Thanks,
On
Hi Jaegeuk,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/ext4/ext4.h
between commit:
c8585c6fcaf2 ("ext4: fix races between changing inode journal mode and
ext4_writepages")
from the ext4 tree and commit:
a618a2a1dda4 ("ext4 crypto: migrate into vfs's crypto
Hi Jaegeuk,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/ext4/ext4.h
between commit:
c8585c6fcaf2 ("ext4: fix races between changing inode journal mode and
ext4_writepages")
from the ext4 tree and commit:
a618a2a1dda4 ("ext4 crypto: migrate into vfs's crypto
12 matches
Mail list logo
