From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752193AbeBIAWl (ORCPT <rfc822;w@1wt.eu>);
        Thu, 8 Feb 2018 19:22:41 -0500
Received: from ozlabs.org ([103.22.144.67]:39561 "EHLO ozlabs.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751317AbeBIAWk (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 8 Feb 2018 19:22:40 -0500
Date: Fri, 9 Feb 2018 11:22:37 +1100
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <mawilcox@microsoft.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: status of the idr tree
Message-ID: <20180209112237.5c9ca99e@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Willy,

Just wondering if I should keep tracking the idr tree
(git://git.infradead.org/users/willy/linux-dax.git#idr-4.11) which
(unsuprisedly) hasn't been updated since March last year.

If there is to be more work in this area, maybe you could create a
for-next branch (or something else release agnostic) for me to track.

-- 
Cheers,
Stephen Rothwell