From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753468AbcEWIh7 (ORCPT ); Mon, 23 May 2016 04:37:59 -0400 Received: from ozlabs.org ([103.22.144.67]:38091 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752897AbcEWIh6 (ORCPT ); Mon, 23 May 2016 04:37:58 -0400 Date: Mon, 23 May 2016 18:37:55 +1000 From: Stephen Rothwell To: Xiong Zhou Cc: Linux-Next , "linux-kernel@vger.kernel.org" Subject: Re: linux-next: Tree for May 17 Message-ID: <20160523183755.412b335c@canb.auug.org.au> In-Reply-To: References: <20160517150412.665a3de4@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: X-Mailing-List: linux-kernel@vger.kernel.org Hi Xiong, On Mon, 23 May 2016 16:13:28 +0800 Xiong Zhou wrote: > > hi, > > On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell wrote: > > > > I have created today's linux-next tree at > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you > > Patches after 0516 are not there. > > i'm chasing an oom issue between 0516 and 0518 trees while missed > 0517 tag, so is the patch file the only way to get there trying 0517 tree? They are there, just the version numbering puts them out of order in the page listing - they appear before patch-v4.6-rc1-next-20160327.gz All the (recent) tags are in the git tree as well, of course. -- Cheers, Stephen Rothwell