From: Mark Brown <broonie@kernel.org>
To: "David.Rau.opensource" <David.Rau.opensource@dm.renesas.com>
Cc: Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"perex@perex.cz" <perex@perex.cz>,
"support.opensource@diasemi.com" <support.opensource@diasemi.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ASoC: da7213: Add support for mono, set frame width to 32 when possible
Date: Mon, 19 Dec 2022 18:12:49 +0000 [thread overview]
Message-ID: <Y6CpoYfr6PPAH3j6@sirena.org.uk> (raw)
In-Reply-To: <OS3PR01MB66410E087BED80930430F72FCDE59@OS3PR01MB6641.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
On Mon, Dec 19, 2022 at 03:52:52AM +0000, David.Rau.opensource wrote:
> Is there anything I should modify or correct to make this commit move forward?
This is a new feature and we're in the merge window so no new features
will be applied at the minute. Please wait till after the merge window.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-19 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 4:40 David Rau
2022-12-14 14:21 ` Mark Brown
[not found] ` <CAG+cZ07erTzV8Re-xo8GixpsEhK28Q6wHxQeE0co+sWgQAFgGA@mail.gmail.com>
2022-12-14 14:56 ` Mark Brown
2022-12-14 16:24 ` Piotr Wojtaszczyk
[not found] ` <OS3PR01MB66410E087BED80930430F72FCDE59@OS3PR01MB6641.jpnprd01.prod.outlook.com>
2022-12-19 18:12 ` Mark Brown [this message]
2022-12-27 11:57 ` 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=Y6CpoYfr6PPAH3j6@sirena.org.uk \
--to=broonie@kernel.org \
--cc=David.Rau.opensource@dm.renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=support.opensource@diasemi.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
all inboxes | Powered by JetHome®