From: Mark Brown <broonie@kernel.org>
To: Cheng-Yi Chiang <cychiang@chromium.org>
Cc: linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>,
Heiko Stuebner <heiko@sntech.de>,
dianders@chromium.org, dgreid@chromium.org, tzungbi@chromium.org,
mka@chromium.org, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] Revert "ASoC: rockchip: i2s: Support mono capture"
Date: Fri, 26 Jul 2019 12:17:17 +0100 [thread overview]
Message-ID: <20190726111717.GB4902@sirena.org.uk> (raw)
In-Reply-To: <20190726044202.26866-1-cychiang@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Fri, Jul 26, 2019 at 12:42:02PM +0800, Cheng-Yi Chiang wrote:
> This reverts commit db51707b9c9aeedd310ebce60f15d5bb006567e0.
>
> Previous discussion in
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
[-- 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: Cheng-Yi Chiang <cychiang@chromium.org>
Cc: alsa-devel@alsa-project.org, tzungbi@chromium.org,
Heiko Stuebner <heiko@sntech.de>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
dianders@chromium.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-rockchip@lists.infradead.org, mka@chromium.org,
dgreid@chromium.org, Jaroslav Kysela <perex@perex.cz>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Revert "ASoC: rockchip: i2s: Support mono capture"
Date: Fri, 26 Jul 2019 12:17:17 +0100 [thread overview]
Message-ID: <20190726111717.GB4902@sirena.org.uk> (raw)
In-Reply-To: <20190726044202.26866-1-cychiang@chromium.org>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
On Fri, Jul 26, 2019 at 12:42:02PM +0800, Cheng-Yi Chiang wrote:
> This reverts commit db51707b9c9aeedd310ebce60f15d5bb006567e0.
>
> Previous discussion in
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-26 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 4:42 [PATCH] Revert "ASoC: rockchip: i2s: Support mono capture" Cheng-Yi Chiang
2019-07-26 4:42 ` Cheng-Yi Chiang
2019-07-26 4:42 ` Cheng-Yi Chiang
2019-07-26 11:17 ` Mark Brown [this message]
2019-07-26 11:17 ` Mark Brown
2019-07-26 12:10 ` Cheng-yi Chiang
2019-07-26 12:10 ` Cheng-yi Chiang
2019-07-26 12:10 ` Cheng-yi Chiang
2019-07-26 12:12 ` Applied "ASoC: rockchip: Fix mono capture" to the asoc tree Mark Brown
2019-07-26 12:12 ` Mark Brown
2019-07-26 12:12 ` 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=20190726111717.GB4902@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mka@chromium.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tzungbi@chromium.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.