From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753839AbeAGM72 (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Sun, 7 Jan 2018 07:59:28 -0500
Received: from mail-ot0-f196.google.com ([74.125.82.196]:35192 "EHLO
        mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752886AbeAGM70 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 7 Jan 2018 07:59:26 -0500
X-Google-Smtp-Source: ACJfBou1OtLjpCmpiqpjbxzUHAjdPUhRSB7keAaOWKbmOe/sSadXHjoFaQ8xLEqy1wAOyXAHh+SUeQ==
Date: Sun, 7 Jan 2018 06:57:42 -0600
From: Steven Eckhoff <steven.eckhoff.opensource@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>, linux-kernel@vger.kernel.org,
        Philippe Ombredanne <pombredanne@nexb.com>,
        Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [alsa-devel][PATCH v7] ASoC: TSCS42xx: Add support for Tempo
 Semiconductor's TSCS42xx audio CODEC
Message-ID: <20180107125741.st3qs4tqu7txs64j@localhost.localdomain>
References: <20171219205415.wlu4atv2mdy7i3gb@localhost.localdomain>
 <20180105123803.GD9076@sirena.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180105123803.GD9076@sirena.org.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On Fri, Jan 05, 2018 at 12:38:03PM +0000, Mark Brown wrote:
> This doesn't apply cleanly against current code, what did you submit
> against?  :(  These aren't trivial things that have just been added to
> my tree in this development cycle either, it looks like you're
> submitting against some older kernel.  I've applied anyway but please be
> careful.
I apologize for this. I created the patch against the master branch and
did not notice that is was las updated 5 years ago. On IRC I was told to
use for-next. I will use that tree to create the next patch against.