Linux virtualization list
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
Cc: benoit.taine@lip6.fr, virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 23/25] virtio: Replace DEFINE_PCI_DEVICE_TABLE macro use
Date: Mon, 21 Jul 2014 10:52:48 +0930	[thread overview]
Message-ID: <87oawjzes7.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1405697232-11785-24-git-send-email-benoit.taine@lip6.fr>

Benoit Taine <benoit.taine@lip6.fr> writes:
> We should prefer `struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to meet
> kernel coding style guidelines. This issue was reported by checkpatch.
>
> Signed-off-by: Benoit Taine <benoit.taine@lip6.fr>

Thanks, applied.

Cheers,
Rusty.

  parent reply	other threads:[~2014-07-21  1:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1405697232-11785-1-git-send-email-benoit.taine@lip6.fr>
2014-07-18 15:27 ` [PATCH 23/25] virtio: Replace DEFINE_PCI_DEVICE_TABLE macro use Benoit Taine
2014-07-18 16:22 ` [PATCH 0/25] " John W. Linville
     [not found] ` <1405700934.605.31.camel@jarvis.lan>
2014-07-18 16:33   ` Keller, Jacob E
     [not found] ` <20140718162213.GC31114@tuxdriver.com>
2014-07-18 16:43   ` Greg KH
2014-07-18 18:05     ` Joe Perches
     [not found]     ` <1405702472.30262.1.camel@dabdike.int.hansenpartnership.com>
2014-07-18 18:17       ` Greg KH
     [not found]       ` <20140718181759.GB2193@kroah.com>
2014-07-18 21:14         ` Dave Airlie
2014-07-18 21:27           ` Greg KH
     [not found]         ` <1405709421.30262.8.camel@dabdike.int.hansenpartnership.com>
2014-07-21 23:16           ` Bjorn Helgaas
2014-07-22 17:12             ` Benoit Taine
     [not found] ` <1405697232-11785-24-git-send-email-benoit.taine@lip6.fr>
2014-07-21  1:22   ` Rusty Russell [this message]
2014-07-21  4:18 ` David Miller

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=87oawjzes7.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=benoit.taine@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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