mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kim, David" <david.kim@ncipher.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Magee, Tim" <tim.magee@ncipher.com>
Subject: RE: [PATCH 1/1] drivers: misc: Add support for nCipher HSM devices
Date: Fri, 20 Dec 2019 15:30:17 +0000	[thread overview]
Message-ID: <f0a52eb552a54a2c8c447145eec9bd47@exukdagfar01.INTERNAL.ROOT.TES> (raw)
In-Reply-To: <20191217133834.GE3362771@kroah.com>

> > +/**
> > + * 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?

We've removed our redefinition of PCI_VENDOR_ID_INTEL and are now using the PCI_DEVICE_SUB macro to define these structs.

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

All the commenting format should be better now.

Thanks,
Dave


David Kim
Senior Software Engineer
Tel: +44 1223 703449

nCipher Security
One Station Square
Cambridge CB1 2GA
United Kingdom


      reply	other threads:[~2019-12-20 15:30 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
2019-12-20 15:30     ` Kim, David [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=f0a52eb552a54a2c8c447145eec9bd47@exukdagfar01.INTERNAL.ROOT.TES \
    --to=david.kim@ncipher.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®