From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1756852AbeAHLU7 (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Mon, 8 Jan 2018 06:20:59 -0500
Received: from heliosphere.sirena.org.uk ([172.104.155.198]:36448 "EHLO
        heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1756078AbeAHLU6 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 8 Jan 2018 06:20:58 -0500
Date: Mon, 8 Jan 2018 11:20:46 +0000
From: Mark Brown <broonie@kernel.org>
To: Steven Eckhoff <steven.eckhoff.opensource@gmail.com>
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 v8] ASoC: TSCS42xx: Add support for Tempo
 Semiconductor's TSCS42xx audio CODEC
Message-ID: <20180108112046.GA11698@sirena.org.uk>
References: <20180107141943.y5hh3cob2uak4sod@localhost.localdomain>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF"
Content-Disposition: inline
In-Reply-To: <20180107141943.y5hh3cob2uak4sod@localhost.localdomain>
X-Cookie: We are what we are.
User-Agent: Mutt/1.9.2 (2017-12-15)
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>


--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 07, 2018 at 08:19:54AM -0600, Steven Eckhoff wrote:
> Currently there is no support for TSCS42xx audio CODECs.
>=20
> Add support for TSCS42xx audio CODECs.

Please don't resubmit patches that have already been applied, you should
submit patches against current code in the tree you're expecting things
to be applied to.  If any updates are needed to a patch that's already
been applied you should submit incremental patches which make those
updates.  This avoids having to change published git commits which could
cause problems for people working against git.

--h31gzZEtNLTqOjlF
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlpTVA0ACgkQJNaLcl1U
h9BDyQf+KAjkajZcneH0vBdstVHBTjsQDMp9xmIaWl0qiXYzYc7t05Zl7cRhSSTx
+ITw4ft3m/dshAshZR8ZM6QzKpyyJoFX8TmfW6bS0666aLeKuSsacMseIEW9aTEo
/U/OmvQDYnQ6M1hPKtviKDglvs7KCsTUvwdoqRU47s+VtNopBy7OHrWlE7X4IHm1
kUOD9sHGDSFiw9lFbexrkCVOWlOqIM1mnjopMZ5vaSZpwjOdhptRUpcNlSZI9HUs
+U3nxlo+8ZAlqby8lhSMu2gB93vfVjli01a8g4RKLOIkO59GJxwpwmQlrOvMtorf
DM72hGd1WGZYuP9YgdwU6XA+Bdj7GQ==
=YMTO
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--