All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dicheng Wang <wangdicheng123@hotmail.com>
Cc: wangdicheng@kylinos.cn, stable@vger.kernel.org
Subject: Re: [PATCH -next] The USB audio driver does not contain the VID and PID of this sound card, so the driver is not loaded.
Date: Fri, 2 Dec 2022 13:44:16 +0100	[thread overview]
Message-ID: <Y4nzIEdMV7h8xU/6@kroah.com> (raw)
In-Reply-To: <SG2PR02MB58786472A08370F924C3E7828A179@SG2PR02MB5878.apcprd02.prod.outlook.com>

On Fri, Dec 02, 2022 at 03:49:34PM +0800, Dicheng Wang wrote:
> From: wangdicheng <wangdicheng@kylinos.cn>
> 
> Add relevant information to the quirks-table.h file.
> The test passes and the sound source file plays normally.
> 
> Cc: stable@vger.kernel.org
> 
> Signed-off-by: wangdicheng <wangdicheng@kylinos.cn>
> ---
>  sound/usb/quirks-table.h | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
> index 874fcf245747..24b8d4fc87c4 100644
> --- a/sound/usb/quirks-table.h
> +++ b/sound/usb/quirks-table.h
> @@ -2801,6 +2801,12 @@ YAMAHA_DEVICE(0x7010, "UB99"),
>  	.idVendor = 0x17cc,
>  	.idProduct = 0x1020,
>  },
> +{
> +	/* Ktmicro Usb_audio */
> +	.match_flags = USB_DEVICE_ID_MATCH_DEVICE,
> +	.idVendor = 0x31b2,
> +	.idProduct = 0x0011,
> +},
>  
>  /* QinHeng devices */
>  {
> -- 
> 2.25.1
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2022-12-02 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  7:49 [PATCH -next] The USB audio driver does not contain the VID and PID of this sound card, so the driver is not loaded Dicheng Wang
2022-12-02 12:44 ` Greg KH [this message]
2022-12-02  8:29 Dicheng Wang
2022-12-02 13:15 ` Takashi Iwai
2022-12-02 13:15   ` Takashi Iwai

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=Y4nzIEdMV7h8xU/6@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=wangdicheng123@hotmail.com \
    --cc=wangdicheng@kylinos.cn \
    /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.