alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Takashi Iwai <tiwai@suse.com>, Bard Liao <bardliao@realtek.com>
Subject: Re: [PATCH v2 00/10] ASoC: rt5640: Add jack-detect and button-press support
Date: Sun, 13 May 2018 06:48:21 +0200	[thread overview]
Message-ID: <87c76437-459c-0c24-f629-d296bb18fec1@redhat.com> (raw)
In-Reply-To: <20180513022956.GB17611@sirena.org.uk>

Hi,

On 05/13/2018 04:29 AM, Mark Brown wrote:
> On Fri, May 11, 2018 at 03:29:18PM +0200, Hans de Goede wrote:
>> Hi Mark, et. al.,
>>
>> Here is v2 of the remaining patches from my rt5640 jack-detect series.
>>
>> As requested this is rebased on your sound/for-next branch, so this should
>> apply cleanly now.
> 
> That's not what git is telling me:
> 
> Applying: ASoC: Intel: bytcr_rt5640: Use device properties for setting up dmic
> error: patch failed: sound/soc/intel/boards/bytcr_rt5640.c:556
> error: sound/soc/intel/boards/bytcr_rt5640.c: patch does not apply
> Patch failed at 0001 ASoC: Intel: bytcr_rt5640: Use device properties for setting up dmic
> Use 'git am --show-current-patch' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> 
> If I try with -3 it tells me that it doesn't even know the SHA1s which
> suggests you have something else in your tree?

Yes, I still have the "ASoC: Intel: bytcr_rt5640: Drop unwanted ignore_suspend settings"
patch, for which we never really finished the discussion.

I will drop that for now and send a v3 which should apply cleanly, sorry about this.

As for the ignore_suspend patch I will run some tests to make sure that things
work ok without it and then just drop it permanently.

Regards,

Hans

      reply	other threads:[~2018-05-13  4:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 13:29 [PATCH v2 00/10] ASoC: rt5640: Add jack-detect and button-press support Hans de Goede
2018-05-11 13:29 ` [PATCH v2 01/10] ASoC: Intel: bytcr_rt5640: Use device properties for setting up dmic Hans de Goede
2018-05-11 13:29 ` [PATCH v2 02/10] ASoC: Intel: bytcr_rt5640: Fix Dell Venue 8 5830 Pro quirk Hans de Goede
2018-05-11 13:29 ` [PATCH v2 03/10] ASoC: Intel: bytcr_rt5640: Enable jack detection Hans de Goede
2018-05-11 13:29 ` [PATCH v2 04/10] ASoC: Intel: bytcr_rt5640: Change BYTCR default input to IN3 Hans de Goede
2018-05-11 13:29 ` [PATCH v2 05/10] ASoC: Intel: bytcr_rt5640: Unify BYTCR input defaults Hans de Goede
2018-05-11 13:29 ` [PATCH v2 06/10] ASoC: Intel: bytcr_rt5640: Add default jack-detect settings Hans de Goede
2018-05-11 13:29 ` [PATCH v2 07/10] ASoC: Intel: bytcr_rt5640: Sort DMI quirk list alphabetically Hans de Goede
2018-05-11 13:29 ` [PATCH v2 08/10] ASoC: Intel: bytcr_rt5640: Use dmi_first_match() for DMI quirk handling Hans de Goede
2018-05-11 13:29 ` [PATCH v2 09/10] ASoC: Intel: bytcr_rt5640: Add quirks for various devices Hans de Goede
2018-05-17 16:38   ` Applied "ASoC: Intel: bytcr_rt5640: Add quirks for various devices" to the asoc tree Mark Brown
2018-05-11 13:29 ` [PATCH v2 10/10] ASoC: Intel: bytcr_rt5640: Set card long_name based on quirks Hans de Goede
2018-05-13  2:29 ` [PATCH v2 00/10] ASoC: rt5640: Add jack-detect and button-press support Mark Brown
2018-05-13  4:48   ` Hans de Goede [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=87c76437-459c-0c24-f629-d296bb18fec1@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).