alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC updates for v4.16
Date: Fri, 12 Jan 2018 15:00:32 +0100	[thread overview]
Message-ID: <s5hlgh3npmn.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180112125751.GB6606@sirena.org.uk>

On Fri, 12 Jan 2018 13:57:51 +0100,
Mark Brown wrote:
> 
> The following changes since commit ba6c29592545635f7c476cbef0db0c4f39495f23:
> 
>   ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC (2018-01-05 12:37:41 +0000)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v4.16-2
> 
> for you to fetch changes up to 4ac71d1b68365915bcde14d0ff8fda186ad377ac:
> 
>   Merge remote-tracking branches 'asoc/topic/wm8994', 'asoc/topic/wm8997' and 'asoc/topic/wm8998' into asoc-next (2018-01-12 12:29:46 +0000)
> 
> ----------------------------------------------------------------
> ASoC: Updates for v4.16
> 
> Some more updates for v4.16, the big things here are the ST DFSDM driver
> and the IIO patches required to support that and even more in the
> neverending series of code quality improvements for x86, including
> Pierre's work to improve the Kconfig.  The unused SN95031 driver and
> associated board support are also removed, they haven't been buildable
> for a considerable time without anyone noticing.

Pulled now.  Thanks!


Takashi

  reply	other threads:[~2018-01-12 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 12:57 [GIT PULL] ASoC updates for v4.16 Mark Brown
2018-01-12 14:00 ` Takashi Iwai [this message]
2018-01-12 18:49   ` Mark Brown
2018-01-12 19:56     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2018-01-29 12:46 Mark Brown
2018-01-05 17:21 Mark Brown
2018-01-05 20:45 ` Takashi Iwai

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=s5hlgh3npmn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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).