From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
alsa-devel@alsa-project.org, Timur Tabi <timur@tabi.org>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
linuxppc-dev@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] Applied "ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20" to the asoc tree
Date: Thu, 30 Nov 2017 11:49:22 +0100 [thread overview]
Message-ID: <s5hefogm47h.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171130104159.r2zgwblievcyfpya@sirena.org.uk>
On Thu, 30 Nov 2017 11:41:59 +0100,
Mark Brown wrote:
>
> On Wed, Nov 29, 2017 at 10:23:23PM +0100, Takashi Iwai wrote:
>
> > Mark, I already took this into my tree, as it's a change in ALSA core
> > stuff. As mentioned in another mail, the branch was exposed to
> > topic/pcm-20bit branch, so that you can pull cleanly.
>
> That's what this is reporting - the result of my pull. My script
> reports all new patches I push rather than things I apply, I pull
> infrequently enough I didn't need to fix it yet.
No problem, I just wanted to confirm. But still it would have been
more helpful if you could tell me it beforehand...
thanks,
Takashi
prev parent reply other threads:[~2017-11-30 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 22:33 [PATCH v4 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S,U}20 Maciej S. Szmigiero
2017-11-29 8:36 ` Takashi Iwai
2017-11-29 19:00 ` Applied "ALSA: pcm: add SNDRV_PCM_FORMAT_{S,U}20" to the asoc tree Mark Brown
2017-11-29 21:23 ` [alsa-devel] Applied "ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20" " Takashi Iwai
2017-11-30 10:41 ` Mark Brown
2017-11-30 10:49 ` Takashi Iwai [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=s5hefogm47h.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mail@maciej.szmigiero.name \
--cc=nicoleotsuka@gmail.com \
--cc=o-takashi@sakamocchi.jp \
--cc=timur@tabi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox