public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Maxim Schwalm <maxim.schwalm@gmail.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH v1 09/10] staging: dsp: add support for Fortemedia FM34NE DSP
Date: Tue, 21 Feb 2023 20:27:44 +0100	[thread overview]
Message-ID: <Y/UbMH5tXDgsvSbD@kroah.com> (raw)
In-Reply-To: <20230221183211.21964-10-clamor95@gmail.com>

On Tue, Feb 21, 2023 at 08:32:10PM +0200, Svyatoslav Ryhel wrote:
> FM34NE is digital sound processing chip used for active
> noise suppression mainly on ASUS Transformers.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
>  drivers/staging/Kconfig          |   2 +
>  drivers/staging/Makefile         |   1 +
>  drivers/staging/dsp/Kconfig      |   7 +
>  drivers/staging/dsp/Makefile     |   2 +
>  drivers/staging/dsp/dsp-fm34ne.c | 364 +++++++++++++
>  drivers/staging/dsp/dsp-fm34ne.h | 845 +++++++++++++++++++++++++++++++
>  6 files changed, 1221 insertions(+)
>  create mode 100644 drivers/staging/dsp/Kconfig
>  create mode 100644 drivers/staging/dsp/Makefile
>  create mode 100644 drivers/staging/dsp/dsp-fm34ne.c
>  create mode 100644 drivers/staging/dsp/dsp-fm34ne.h


Sorry, but why is this going into drivers/staging/ at all?  What is
needed to be done to get this out of staging?  Why not do that work
right now?  At the least, we need a TODO file in the directory that
lists what needs to be done and who is responsible for it.

But again, just do the work now, it's faster and simpler to do it before
you submit it instead of waiting until after it is merged.

Also, no need for a .h file when you only have one .c file.  Just put
them all together into one file please.

thanks,

greg k-h

  reply	other threads:[~2023-02-21 19:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 18:32 [PATCH v1 00/10] Fix sound on ASUS Transformers Svyatoslav Ryhel
2023-02-21 18:32 ` [PATCH v1 01/10] dt-bindings: sound: nvidia,tegra-audio-common: add new property Svyatoslav Ryhel
2023-02-26 19:35   ` Rob Herring
2023-02-21 18:32 ` [PATCH v1 02/10] sound: soc: jack: allow multiple interrupt per gpio Svyatoslav Ryhel
2023-02-21 22:08   ` Mark Brown
2023-02-22  7:53     ` Svyatoslav Ryhel
2023-02-22 12:16       ` Mark Brown
2023-02-21 18:32 ` [PATCH v1 03/10] dt-bindings: sound: nvidia,tegra-audio: add RT5631 CODEC Svyatoslav Ryhel
2023-02-26 19:37   ` Rob Herring
2023-02-28  8:15   ` Krzysztof Kozlowski
2023-02-21 18:32 ` [PATCH v1 04/10] ASoC: tegra: Support RT5631 by machine driver Svyatoslav Ryhel
2023-02-21 19:32   ` Dan Carpenter
2023-02-22  7:55     ` Svyatoslav Ryhel
2023-02-22 13:28       ` Dan Carpenter
2023-02-22 14:57         ` Mark Brown
2023-02-21 22:23   ` Mark Brown
2023-02-22  8:00     ` Svyatoslav Ryhel
2023-02-22 12:17       ` Mark Brown
2023-02-21 18:32 ` [PATCH v1 05/10] dt-bindings: sound: nvidia,tegra-audio: add MAX9808x CODEC Svyatoslav Ryhel
2023-02-26 19:38   ` Rob Herring
2023-02-21 18:32 ` [PATCH v1 06/10] ASoC: tegra: Support MAX9808x by machine driver Svyatoslav Ryhel
2023-02-21 18:32 ` [PATCH v1 07/10] ARM: tegra: transformers: update bindings of sound graph Svyatoslav Ryhel
2023-02-21 22:26   ` Mark Brown
2023-02-22  8:02     ` Svyatoslav Ryhel
2023-02-22 12:19       ` Mark Brown
2023-02-21 18:32 ` [PATCH v1 08/10] dt-bindings: dsp: add Fortemedia FM34 DSP Svyatoslav Ryhel
2023-02-26 19:42   ` Rob Herring
2023-02-21 18:32 ` [PATCH v1 09/10] staging: dsp: add support for Fortemedia FM34NE DSP Svyatoslav Ryhel
2023-02-21 19:27   ` Greg Kroah-Hartman [this message]
2023-02-22  8:19     ` Svyatoslav Ryhel
2023-02-22  9:21       ` Greg Kroah-Hartman
2023-02-22  9:39         ` Святослав Ригель
2023-02-22 11:15           ` Greg Kroah-Hartman
2023-02-22 12:19       ` Mark Brown
2023-02-21 19:39   ` Dan Carpenter
2023-02-22  8:06     ` Svyatoslav Ryhel
2023-02-22 13:31       ` Dan Carpenter
2023-02-21 22:41   ` Mark Brown
2023-02-22  8:14     ` Svyatoslav Ryhel
2023-02-22 12:36       ` Mark Brown
2023-02-21 18:32 ` [PATCH v1 10/10] ARM: tegra: transformers: bind FM34NE DSP on supported devices Svyatoslav Ryhel
2023-03-06 13:31 ` (subset) [PATCH v1 00/10] Fix sound on ASUS Transformers 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=Y/UbMH5tXDgsvSbD@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maxim.schwalm@gmail.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.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