i40evf: remove unused device ID - net-next.git

diff options

author	Mitch Williams <mitch.a.williams@intel.com>	2016-11-11 12:39:39 -0800
committer	Jeff Kirsher <jeffrey.t.kirsher@intel.com>	2017-02-02 22:40:09 -0800
commit	17901e1bde9b959b535d075f137d5a86ca64f1c9 (patch)
tree	a661dba742174be74edab094ac2205730d5c3149 /sound/core/Makefile
parent	6de432c5ae28e7330e14e85c4c614a67a0a12263 (diff)

i40evf: remove unused device ID

This device ID was intended for use when running Linux VF drivers under Hyper-V, but we have determined that it is not necessary. Since it is unused, and will never be used, remove it. Change-ID: I74998ab4237db043cd400547bb54a0a5e2a37ea5 Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

Diffstat (limited to 'sound/core/Makefile')

0 files changed, 0 insertions, 0 deletions

ref='/cgit.cgi/linux/net-next.git/diff/sound/pci/echoaudio/indigoiox.c?h=nds-private-remove&id=4759d386d55fef452d692bf101167914437e848e&id2=1db175428ee374489448361213e9c3b749d14900'>diff)

Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm

Pull DAX updates from Dan Williams: "The completion of Jan's DAX work for 4.10. As I mentioned in the libnvdimm-for-4.10 pull request, these are some final fixes for the DAX dirty-cacheline-tracking invalidation work that was merged through the -mm, ext4, and xfs trees in -rc1. These patches were prepared prior to the merge window, but we waited for 4.10-rc1 to have a stable merge base after all the prerequisites were merged. Quoting Jan on the overall changes in these patches: "So I'd like all these 6 patches to go for rc2. The first three patches fix invalidation of exceptional DAX entries (a bug which is there for a long time) - without these patches data loss can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks

Diffstat (limited to 'sound/pci/echoaudio/indigoiox.c')


context:
space:
mode: