All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] ASoC: tlv320aic31xx: Add headphone/headset detection
Date: Tue, 4 Sep 2018 16:52:31 +0100	[thread overview]
Message-ID: <20180904155231.GI12993@sirena.org.uk> (raw)
In-Reply-To: <20180904153619.2199-2-afd@ti.com>

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

On Tue, Sep 04, 2018 at 10:36:18AM -0500, Andrew F. Davis wrote:
> This device can detect the insertion/removal of headphones and headsets.
> Enable reporting this status by enabling this interrupt and forwarding
> this to upper-layers if a jack has been defined.

This doesn't apply against current code (even -next) - please check and
resend:

$ git am -3 --signoff /tmp/fnord
Applying: ASoC: tlv320aic31xx: Add overflow detection support
Applying: ASoC: tlv320aic31xx: Add headphone/headset detection
error: sha1 information is lacking or useless (sound/soc/codecs/tlv320aic31xx.c).
error: could not build fake ancestor

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] ASoC: tlv320aic31xx: Add headphone/headset detection
Date: Tue, 4 Sep 2018 16:52:31 +0100	[thread overview]
Message-ID: <20180904155231.GI12993@sirena.org.uk> (raw)
In-Reply-To: <20180904153619.2199-2-afd@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 623 bytes --]

On Tue, Sep 04, 2018 at 10:36:18AM -0500, Andrew F. Davis wrote:
> This device can detect the insertion/removal of headphones and headsets.
> Enable reporting this status by enabling this interrupt and forwarding
> this to upper-layers if a jack has been defined.

This doesn't apply against current code (even -next) - please check and
resend:

$ git am -3 --signoff /tmp/fnord
Applying: ASoC: tlv320aic31xx: Add overflow detection support
Applying: ASoC: tlv320aic31xx: Add headphone/headset detection
error: sha1 information is lacking or useless (sound/soc/codecs/tlv320aic31xx.c).
error: could not build fake ancestor

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-09-04 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 15:36 [PATCH v2 1/3] ASoC: tlv320aic31xx: Add overflow detection support Andrew F. Davis
2018-09-04 15:36 ` Andrew F. Davis
2018-09-04 15:36 ` [PATCH v2 2/3] ASoC: tlv320aic31xx: Add headphone/headset detection Andrew F. Davis
2018-09-04 15:36   ` Andrew F. Davis
2018-09-04 15:52   ` Mark Brown [this message]
2018-09-04 15:52     ` Mark Brown
2018-09-04 15:36 ` [PATCH v2 3/3] ASoC: tlv320aic31xx: Add button press detection Andrew F. Davis
2018-09-04 15:36   ` Andrew F. Davis
2018-09-04 16:22 ` Applied "ASoC: tlv320aic31xx: Add overflow detection support" to the asoc tree Mark Brown

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=20180904155231.GI12993@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=afd@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.