All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: PAGE_CACHE_* removal in 4.6-rc3
Date: Wed, 13 Apr 2016 07:17:53 +1000	[thread overview]
Message-ID: <20160412211753.GL567@dastard> (raw)
In-Reply-To: <20160412183105.GA10567@infradead.org>

On Tue, Apr 12, 2016 at 11:31:05AM -0700, Christoph Hellwig wrote:
> Hi Dave,
> 
> upstream removed the PAGE_CACHE_* macros in 4.6-rc3, which will cause
> all kinds of interesting conflicts for FS work.  Maybe it's a good idea
> to rebase for-next ontop of -rc3 so that we can sort this out early?

Yeah, I was thinking of doing that when I saw that this was merged.

I've got a bit of stuff to sort out today, but I'll see what I can
do about moving the master branch forward and rebasing the for-next
branch on top of it.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-04-12 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 18:31 PAGE_CACHE_* removal in 4.6-rc3 Christoph Hellwig
2016-04-12 21:17 ` Dave Chinner [this message]

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=20160412211753.GL567@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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.