linux-kernel - Re: [media 7/7] PCI bridge driver for PT3 & PXQ3PE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKnK8-TjJcohucT-cAViSTXyMD2+HL_GY-jDhUApLKVoxOsc-g@mail.gmail.com>
Date:	Tue, 16 Feb 2016 11:07:26 +0900
From:	"AreMa Inc." <info@....ma>
To:	kbuild test robot <lkp@...el.com>
Cc:	kbuild-all@...org, linux-media <linux-media@...r.kernel.org>,
	linux-kernel@...r.kernel.org, Antti Palosaari <crope@....fi>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Mauro Carvalho Chehab <mchehab@....samsung.com>,
	Hans De Goede <hdegoede@...hat.com>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Michael Krufky <mkrufky@...uxtv.org>,
	Sylwester Nawrocki <sylvester.nawrocki@...il.com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	Peter Senna Tschudin <peter.senna@...il.com>
Subject: Re: [media 7/7] PCI bridge driver for PT3 & PXQ3PE

2016-02-15 21:57 GMT+09:00 kbuild test robot <lkp@...el.com>:
> Hi Буди,
>
> [auto build test ERROR on linuxtv-media/master]
> [cannot apply to v4.5-rc4 next-20160215]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url:    https://github.com/0day-ci/linux/commits/info-are-ma/Driver-bundle-for-PT3-PX-Q3PE/20160215-173307
> base:   git://linuxtv.org/media_tree.git master
> config: x86_64-allyesconfig (attached as .config)
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64

We tried to reproduce. It compiles successfully. Nothing wrong.
Your attached .config is corrupted, it doesn't match the kernel
mentioned (v4.5-rc4 next-20160215).
Remaking .config solved the problem. Voila!