linux-kernel - Re: [PATCH v2 -next] ALSA:usb-audio:Add the information of KT0206 device driven by USB audio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y480pd/XynYddrHk@kroah.com>
Date:   Tue, 6 Dec 2022 13:25:09 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Dicheng Wang <wangdicheng123@...mail.com>
Cc:     perex@...ex.cz, tiwai@...e.com, sdoregor@...re.me,
        connerknoxpublic@...il.com, wangdicheng@...inos.cn,
        hahnjo@...njo.de, john-linux@...ago.org.uk,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH v2 -next] ALSA:usb-audio:Add the information of KT0206
 device driven by USB audio

On Tue, Dec 06, 2022 at 05:36:37PM +0800, Dicheng Wang wrote:
> From: wangdicheng <wangdicheng@...inos.cn>
> 
> Cc: stable@...r.kernel.org
> Signed-off-by: wangdicheng <wangdicheng@...inos.cn>
> ---
> v2:use USB_DEVICE_VENDOR_SPEC() suggested by Takashi Iwai
> 
>  sound/usb/quirks-table.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
> index 874fcf245747..271884e35003 100644
> --- a/sound/usb/quirks-table.h
> +++ b/sound/usb/quirks-table.h
> @@ -76,6 +76,8 @@
>  { USB_DEVICE_VENDOR_SPEC(0x041e, 0x3f0a) },
>  /* E-Mu 0204 USB */
>  { USB_DEVICE_VENDOR_SPEC(0x041e, 0x3f19) },
> +/* Ktmicro Usb_audio device */
> +{ USB_DEVICE_VENDOR_SPEC(0x31b2, 0x0011) },
>  
>  /*
>   * Creative Technology, Ltd Live! Cam Sync HD [VF0770]
> -- 
> 2.25.1
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch contains warnings and/or errors noticed by the
  scripts/checkpatch.pl tool.

- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
  and can not be applied.  Please read the file,
  Documentation/email-clients.txt in order to fix this.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what is needed in order to
  properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what a proper Subject: line should
  look like.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file, Documentation/SubmittingPatches
  for how to do this correctly.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot