All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: torvalds@linux-foundation.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Salah Triki <salah.triki@gmail.com>,
	Theodore Ts'o <tytso@mit.edu>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Fabian Frederick <fabf@skynet.be>
Subject: [GIT PULL] fs/befs/
Date: Fri, 05 May 2017 11:52:42 +0100	[thread overview]
Message-ID: <590C597A.2060806@osg.samsung.com> (raw)

Hi Linus,

Third git pull request since I took maintainership of the befs file system [0].

This time it is a light one.
One fix from Fabian Frederick making the nfs client still work after a cache
drop.

Thank you very much,
Luis


[0] https://lkml.org/lkml/2016/7/27/502


The following changes since commit a351e9b9fc24e982ec2f0e76379a49826036da12:

  Linux 4.11 (2017-04-30 19:47:48 -0700)

are available in the git repository at:

  https://github.com/luisbg/linux-befs.git tags/befs-v4.12-rc1

for you to fetch changes up to dcfd9b215b89d72c1053a717571d52bf96cc64f8:

  befs: make export work with cold dcache (2017-05-05 11:35:35 +0100)

----------------------------------------------------------------
befs fixes for 4.12-rc1

----------------------------------------------------------------
Fabian Frederick (1):
      befs: make export work with cold dcache

 fs/befs/linuxvfs.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

             reply	other threads:[~2017-05-05 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 10:52 Luis de Bethencourt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-22 12:18 [GIT PULL] fs/befs/ Luis de Bethencourt
2016-10-15 18:56 Luis de Bethencourt

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=590C597A.2060806@osg.samsung.com \
    --to=luisbg@osg.samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=fabf@skynet.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier@dowhile0.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=salah.triki@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    /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.