All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sandeep Singh <Sandeep.Singh@amd.com>
Cc: mathias.nyman@intel.com, bhelgaas@google.com,
	dheitmueller@kernellabs.com, stern@rowland.harvard.edu,
	samuel.thibault@ens-lyon.org, lukas@oxygene.sk,
	linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	Nehal Shah <Nehal-bakulchandra.Shah@amd.com>
Subject: Re: [PATCH] usb: xhci: Add quirk for Certain failing HP keyboard on reset after resume
Date: Sun, 30 Jul 2017 07:11:59 -0700	[thread overview]
Message-ID: <20170730141159.GA21849@kroah.com> (raw)
In-Reply-To: <1501144509-19357-1-git-send-email-Sandeep.Singh@amd.com>

On Thu, Jul 27, 2017 at 02:05:09PM +0530, Sandeep Singh wrote:
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index c71e532..d3f2296 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -583,6 +583,7 @@
>  #define PCI_DEVICE_ID_AMD_HUDSON2_SMBUS		0x780b
>  #define PCI_DEVICE_ID_AMD_HUDSON2_IDE		0x780c
>  #define PCI_DEVICE_ID_AMD_KERNCZ_SMBUS  0x790b
> +#define PCI_DEVICE_ID_AMD_TAISHAN	0x145c
>  
>  #define PCI_VENDOR_ID_TRIDENT		0x1023
>  #define PCI_DEVICE_ID_TRIDENT_4DWAVE_DX	0x2000

Please read the top of this file for why you shouldn't be adding new ids
to it.

thnaks,

greg k-h

  reply	other threads:[~2017-07-30 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  8:35 [PATCH] usb: xhci: Add quirk for Certain failing HP keyboard on reset after resume Sandeep Singh
2017-07-30 14:11 ` Greg KH [this message]
2017-07-31  6:40   ` Sandeep Singh
2017-07-31 15:46     ` Greg KH

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=20170730141159.GA21849@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Sandeep.Singh@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=bhelgaas@google.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@oxygene.sk \
    --cc=mathias.nyman@intel.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stern@rowland.harvard.edu \
    /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.