From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932279AbdJJOCe convert rfc822-to-8bit (ORCPT ); Tue, 10 Oct 2017 10:02:34 -0400 Received: from mail.savoirfairelinux.com ([208.88.110.44]:58652 "EHLO mail.savoirfairelinux.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932126AbdJJOCb (ORCPT ); Tue, 10 Oct 2017 10:02:31 -0400 Date: Tue, 10 Oct 2017 10:02:30 -0400 (EDT) From: =?utf-8?Q?Jean-Fran=C3=A7ois_T=C3=AAtu?= To: Mark Brown Cc: alsa-devel@alsa-project.org, Srinivas Kandagatla , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , linux-kernel@vger.kernel.org Message-ID: <1309357099.59181.1507644150099.JavaMail.zimbra@savoirfairelinux.com> In-Reply-To: <20171009083147.iwugpdgx2zcw6fyu@sirena.co.uk> References: <20171006180951.10930-1-jean-francois.tetu@savoirfairelinux.com> <20171009083147.iwugpdgx2zcw6fyu@sirena.co.uk> Subject: Re: [RESEND PATCH] ASoC: codecs: msm8916-wcd-digital: fix RX2 MIX1 and RX3 MIX1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Mailer: Zimbra 8.6.0_GA_1153 (ZimbraWebClient - GC58 (Linux)/8.6.0_GA_1153) Thread-Topic: ASoC: codecs: msm8916-wcd-digital: fix RX2 MIX1 and RX3 MIX1 Thread-Index: PktLoK9TxmyQeE9hKCCP8H0pLNnreQ== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Mon, Oct 09, 2017 4:31:46 AM, Mark Brown wrote: >On Fri, Oct 06, 2017 at 02:09:51PM -0400, Jean-François Têtu wrote: >> The kcontrol for the third input (rxN_mix1_inp3) of both RX2 >> and RX3 mixers are not using the correct control register. This simple >> patch fixes this. > > 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. Oops, I'm sorry. I did look in for-next and saw that the patch was there. But, since I did not receive the "Applied" email or an ack from Srinivas, I assumed that the patch was simply ignored and felt I should resend it. -- Jean-François Têtu