From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: Status of sparse-next Date: Mon, 12 Jun 2017 00:46:31 +0200 Message-ID: <20170611224629.ak7evynf6lcyorz7@ltop.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wr0-f169.google.com ([209.85.128.169]:33686 "EHLO mail-wr0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751912AbdFKWqg (ORCPT ); Sun, 11 Jun 2017 18:46:36 -0400 Received: by mail-wr0-f169.google.com with SMTP id v104so78512355wrb.0 for ; Sun, 11 Jun 2017 15:46:36 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Dibyendu Majumdar Cc: Linux-Sparse On Sun, Jun 11, 2017 at 11:02:40PM +0100, Dibyendu Majumdar wrote: > Hi > > I was wondering if the sparse-next branch is going to be stable soon. As far as I know, sparse-next is very stable. Are you aware of any instability? But yes, all the LLVM patches I suppose you're interested in haven't yet made it and sparse-next itself still need to be promoted to master. -- Luc Van Oostenryck