From: "Jean-François Têtu" <jean-francois.tetu@savoirfairelinux.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] ASoC: codecs: msm8916-wcd-digital: fix RX2 MIX1 and RX3 MIX1
Date: Tue, 10 Oct 2017 10:02:30 -0400 (EDT) [thread overview]
Message-ID: <1309357099.59181.1507644150099.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20171009083147.iwugpdgx2zcw6fyu@sirena.co.uk>
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
prev parent reply other threads:[~2017-10-10 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 18:09 Jean-François Têtu
2017-10-09 8:31 ` Mark Brown
2017-10-10 14:02 ` Jean-François Têtu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309357099.59181.1507644150099.JavaMail.zimbra@savoirfairelinux.com \
--to=jean-francois.tetu@savoirfairelinux.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®