Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: please clean up the fscache tree
Date: Wed, 3 Aug 2016 11:15:10 +1000	[thread overview]
Message-ID: <20160803111510.65620fc7@canb.auug.org.au> (raw)

Hi David,

The fscache tree
(git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git#fscache)
only contains 2 commits:

b00c2ae2ed3c FS-Cache: Don't override netfs's primary_index if registering failed
3c9b3b74606d FS-Cache: Increase reference of parent after registering, netfs success

which also exist in Linus' tree as other commits (they were merged in
Nov, 2015 via Al Viro).

Please clean this up, or let me know if it is not going to be used any
more and I will delete the tree from linux-next.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-08-03  1:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  1:15 Stephen Rothwell [this message]
2016-08-03 13:30 ` linux-next: please clean up the fscache tree David Howells

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=20160803111510.65620fc7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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