From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Gromm <christian.gromm@microchip.com>
Cc: driverdev-devel@linuxdriverproject.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v3] drivers: most: add ALSA sound driver
Date: Tue, 23 Mar 2021 10:04:15 +0100 [thread overview]
Message-ID: <YFmvD/oYW8ihe+ez@kroah.com> (raw)
In-Reply-To: <1612865627-29950-1-git-send-email-christian.gromm@microchip.com>
On Tue, Feb 09, 2021 at 11:13:47AM +0100, Christian Gromm wrote:
> This patch moves the ALSA sound driver out of the staging area and adds it
> to the stable part of the MOST driver. Modifications to the Makefiles and
> Kconfigs are done accordingly to not break the build.
>
> Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
> ---
> v2:
> Reported-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> submitted patch that fixes issue found during code audit
> to staging version first to be able to resend single patch that
> adds the driver. The patch series included:
>
> - use swabXX functions of kernel
>
> v3:
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> - use non-safe list iteration
> - add sanity check for function argument
Given a lack of complaints about this, I've now queued this up in my
staging tree for the next -rc1 merge window, thanks!
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2021-03-23 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 10:13 [PATCH v3] drivers: most: add ALSA sound driver Christian Gromm
2021-03-23 9:04 ` Greg KH [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=YFmvD/oYW8ihe+ez@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christian.gromm@microchip.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=linux-sound@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).