linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Dimitris Michailidis <d.michailidis@fungible.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	andrew@lunn.ch, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/8] PCI: add Fungible vendor ID to pci_ids.h
Date: Fri, 7 Jan 2022 11:48:36 -0600	[thread overview]
Message-ID: <20220107174836.GA388004@bhelgaas> (raw)
In-Reply-To: <20220107043612.21342-2-dmichail@fungible.com>

On Thu, Jan 06, 2022 at 08:36:05PM -0800, Dimitris Michailidis wrote:
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org
> Signed-off-by: Dimitris Michailidis <dmichail@fungible.com>

Acked-by: Bjorn Helgaas <bhelgaas@google.com>

If you repost this for any reason, please capitalize the subject line
so it matches the history, e.g.,

  3375590623e4 ("PCI: Add Zhaoxin Vendor ID")
  4460d68f0b2f ("PCI: Add Genesys Logic, Inc. Vendor ID")

> ---
>  include/linux/pci_ids.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 011f2f1ea5bb..c4299dbade98 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2578,6 +2578,8 @@
>  
>  #define PCI_VENDOR_ID_HYGON		0x1d94
>  
> +#define PCI_VENDOR_ID_FUNGIBLE		0x1dad
> +
>  #define PCI_VENDOR_ID_HXT		0x1dbf
>  
>  #define PCI_VENDOR_ID_TEKRAM		0x1de1
> -- 
> 2.25.1
> 

      reply	other threads:[~2022-01-07 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220107043612.21342-1-dmichail@fungible.com>
2022-01-07  4:36 ` [PATCH net-next v5 1/8] PCI: add Fungible vendor ID to pci_ids.h Dimitris Michailidis
2022-01-07 17:48   ` Bjorn Helgaas [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=20220107174836.GA388004@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=d.michailidis@fungible.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@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).