linux-kernel - Re: [PATCH char-misc] mei: bus: () can be static

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: <20150302235653.GA3501@wfg-t540p.sh.intel.com>
Date:	Tue, 3 Mar 2015 07:56:53 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Tomas Winkler <tomas.winkler@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	linux-kernel@...r.kernel.org, Nick Meier <nmeier@...rosoft.com>,
	kbuild-all@...org, devel@...uxdriverproject.org
Subject: Re: [PATCH char-misc] mei: bus: () can be static

On Mon, Mar 02, 2015 at 12:41:05PM +0300, Dan Carpenter wrote:
> On Mon, Mar 02, 2015 at 11:49:23AM +0800, kbuild test robot wrote:
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyperv_panic_event' was not declared. Should it be static?
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyperv_panic_event' was not declared. Should it be static?
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyperv_panic_event' was not declared. Should it be static?
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyperv_panic_event' was not declared. Should it be static?
> 
> The subject and the patch don't match.

Sorry it's a bug. Root cause is, char-misc is a non-rebaseable tree,
so the script checks out the branch HEAD before generating the patch.
Then it gets the wrong title (which is based on the HEAD commit's subject).
Fixed now.

Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/