mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Kim <david.kim@ncipher.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	Tim Magee <tim.magee@ncipher.com>
Subject: Re: [PATCH 1/1] drivers: misc: Add support for nCipher HSM devices
Date: Tue, 17 Dec 2019 14:38:34 +0100	[thread overview]
Message-ID: <20191217133834.GE3362771@kroah.com> (raw)
In-Reply-To: <20191217132244.14768-2-david.kim@ncipher.com>

On Tue, Dec 17, 2019 at 01:22:44PM +0000, Dave Kim wrote:
> +/**
> + * PCI device ID table.  We use the driver_data field to hold an index into
> + * nfp_drvlist, so bear than in mind when editing either.
> + */
> +static struct pci_device_id nfp_pci_tbl[] = {
> +	{
> +		PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_21555,
> +		PCI_VENDOR_ID_NCIPHER, PCI_SUBSYSTEM_ID_NFAST_REV1, 0,
> +		0, /* Ignore class */
> +		0 /* Index into nfp_drvlist */

Please use the correct PCI_DEVICE() macros, that should work here,
right?

And you are grabbing an Intel PCI device id?

> +	},
> +	{
> +		PCI_VENDOR_ID_FREESCALE, PCI_DEVICE_ID_FREESCALE_T1022,
> +		PCI_VENDOR_ID_NCIPHER, PCI_SUBSYSTEM_ID_NFAST_REV1, 0,
> +		0, /* Ignore class */
> +		1 /* Index into nfp_drvlist */

Again, PCI_DEVICE() macros please.

And kerneldoc everywhere, your commenting format for all of the code is
a bit "odd".

thanks,

greg k-h

  parent reply	other threads:[~2019-12-17 13:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 13:22 [PATCH 0/1] " Dave Kim
2019-12-17 13:22 ` [PATCH 1/1] " Dave Kim
2019-12-17 13:32   ` Greg KH
2019-12-17 13:53     ` Kim, David
2019-12-17 14:05       ` Greg KH
2019-12-20 15:50     ` Kim, David
2019-12-17 13:36   ` Greg KH
2019-12-20 15:27     ` Kim, David
2019-12-17 13:37   ` Greg KH
2019-12-17 13:38   ` Greg KH [this message]
2019-12-20 15:30     ` Kim, David

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=20191217133834.GE3362771@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=david.kim@ncipher.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.magee@ncipher.com \
    /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

Powered by JetHome