public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* PAGE_CACHE_* removal in 4.6-rc3
@ 2016-04-12 18:31 Christoph Hellwig
  2016-04-12 21:17 ` Dave Chinner
  0 siblings, 1 reply; 2+ messages in thread
From: Christoph Hellwig @ 2016-04-12 18:31 UTC (permalink / raw)
  To: david; +Cc: xfs

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?

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: PAGE_CACHE_* removal in 4.6-rc3
  2016-04-12 18:31 PAGE_CACHE_* removal in 4.6-rc3 Christoph Hellwig
@ 2016-04-12 21:17 ` Dave Chinner
  0 siblings, 0 replies; 2+ messages in thread
From: Dave Chinner @ 2016-04-12 21:17 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: xfs

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-04-12 21:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-12 18:31 PAGE_CACHE_* removal in 4.6-rc3 Christoph Hellwig
2016-04-12 21:17 ` Dave Chinner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox