All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Bluecherry Maintainers <maintainers@bluecherrydvr.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	Kalle Valo <kvalo@codeaurora.org>, Joe Perches <joe@perches.com>,
	Jiri Slaby <jslaby@suse.com>,
	devel@driverdev.osuosl.org, kernel-mentors@selenic.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] Add tw5864 driver
Date: Sun, 13 Mar 2016 19:24:58 -0700	[thread overview]
Message-ID: <20160314022458.GA4036@kroah.com> (raw)
In-Reply-To: <1457920514-20792-1-git-send-email-andrey_utkin@fastmail.com>

On Mon, Mar 14, 2016 at 03:55:14AM +0200, Andrey Utkin wrote:
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2333,6 +2333,7 @@
>  #define PCI_VENDOR_ID_CAVIUM		0x177d
>  
>  #define PCI_VENDOR_ID_TECHWELL		0x1797
> +#define PCI_DEVICE_ID_TECHWELL_5864	0x5864
>  #define PCI_DEVICE_ID_TECHWELL_6800	0x6800
>  #define PCI_DEVICE_ID_TECHWELL_6801	0x6801
>  #define PCI_DEVICE_ID_TECHWELL_6804	0x6804

Please read the comments at the top of this file for why you don't need
to put any new ids into it.

thanks,

greg k-h

  reply	other threads:[~2016-03-14  2:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  1:54 [PATCH] Add tw5864 driver - cover letter Andrey Utkin
2016-03-14  1:55 ` [PATCH] Add tw5864 driver Andrey Utkin
2016-03-14  2:24   ` Greg Kroah-Hartman [this message]
2016-03-14  3:32   ` Greg Kroah-Hartman
2016-03-15 14:07   ` Dan Carpenter
2016-03-17  7:57   ` Leon Romanovsky
  -- strict thread matches above, loose matches on Subject: below --
2016-03-14  1:58 [PATCH] Add tw5864 driver - cover letter Andrey Utkin
2016-03-14  1:59 ` [PATCH] Add tw5864 driver Andrey Utkin
2016-03-14  2:07   ` Joe Perches
2016-03-14  8:06   ` Hans Verkuil
2016-03-14 11:15   ` Mauro Carvalho Chehab

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=20160314022458.GA4036@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrey_utkin@fastmail.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=jslaby@suse.com \
    --cc=kernel-mentors@selenic.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maintainers@bluecherrydvr.com \
    --cc=mchehab@osg.samsung.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 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.