From: Fengguang Wu <fengguang.wu@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, Nick Meier <nmeier@microsoft.com>,
kbuild-all@01.org, devel@linuxdriverproject.org
Subject: Re: [PATCH char-misc] mei: bus: () can be static
Date: Tue, 3 Mar 2015 07:56:53 +0800 [thread overview]
Message-ID: <20150302235653.GA3501@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20150302094105.GF5386@mwanda>
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
next prev parent reply other threads:[~2015-03-02 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 3:49 [char-misc:char-misc-testing 25/45] drivers/hv/vmbus_drv.c:67:9: sparse: constant 0x8000000000000000 is so big it is unsigned long kbuild test robot
2015-03-02 3:49 ` [PATCH char-misc] mei: bus: () can be static kbuild test robot
2015-03-02 9:41 ` Dan Carpenter
2015-03-02 9:47 ` Winkler, Tomas
2015-03-02 23:56 ` Fengguang Wu [this message]
2015-03-02 21:57 ` Nick Meier
2015-03-02 21:55 ` [char-misc:char-misc-testing 25/45] drivers/hv/vmbus_drv.c:67:9: sparse: constant 0x8000000000000000 is so big it is unsigned long Nick Meier
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=20150302235653.GA3501@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmeier@microsoft.com \
--cc=tomas.winkler@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®