From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: linux-next: strange update of the sound tree Date: Mon, 05 Jun 2017 18:32:54 +0200 Message-ID: References: <20170606001723.7950a514@canb.auug.org.au> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mx2.suse.de ([195.135.220.15]:33440 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754037AbdFEQdL (ORCPT ); Mon, 5 Jun 2017 12:33:11 -0400 In-Reply-To: <20170606001723.7950a514@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List On Mon, 05 Jun 2017 16:17:23 +0200, Stephen Rothwell wrote: > > Hi Takashi, > > I don't think you have the result in the sound tree > (git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git > branch for-next). Yesterday it was a fairly linear tree with head > commit 7421a1671abe ("ALSA: pcm: include pcm_local.h and remove some > extraneous tabs") based on commit f83914fdfcc3 ("ALSA: usb-audio: fix > Amanero Combo384 quirk on big-endian hosts"). Now it is a tree with > 687 commits (realative to Linus' tree) with 651 merge commits in it. :-( Doh, I pushed out a wrong branch (master) to for-next, as I had to work on another machine at home today due to a holiday. Now the correct branch was pushed. Sorry for inconvenience, and thanks for catching it. Takashi