From: kbuild test robot <lkp@intel.com>
To: mohammed.billoo@gmail.com
Cc: kbuild-all@01.org, johnny.kim@atmel.com, austin.shin@atmel.com,
chris.park@atmel.com, tony.cho@atmel.com, glen.lee@atmel.com,
leo.kim@atmel.com, gregkh@linuxfoundation.org,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ensure that comments adhere to coding standard
Date: Mon, 4 Apr 2016 02:45:04 +0800 [thread overview]
Message-ID: <201604040250.VHqw9hVI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459707526-21124-1-git-send-email-mohammed.billoo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi Mohammed,
[auto build test WARNING on v4.6-rc2]
[cannot apply to staging/staging-testing next-20160401]
[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/mohammed-billoo-gmail-com/Ensure-that-comments-adhere-to-coding-standard/20160404-022342
config: x86_64-randconfig-x010-201614 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from drivers/staging/wilc1000/wilc_wlan_cfg.c:10:0:
>> drivers/staging/wilc1000/wilc_wlan_cfg.h:2:1: warning: "/*" within comment [-Wcomment]
/* Copyright (c) Atmel Corporation. All rights reserved.
^
vim +2 drivers/staging/wilc1000/wilc_wlan_cfg.h
1 /*
> 2 /* Copyright (c) Atmel Corporation. All rights reserved.
3 *
4 * Module Name: wilc_wlan_cfg.h
5 */
6
7 #ifndef WILC_WLAN_CFG_H
8 #define WILC_WLAN_CFG_H
9
10 struct wilc_cfg_byte {
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 32342 bytes --]
prev parent reply other threads:[~2016-04-03 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 18:18 mohammed.billoo
2016-04-03 18:41 ` Greg KH
2016-04-03 18:45 ` kbuild test robot [this message]
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=201604040250.VHqw9hVI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=kbuild-all@01.org \
--cc=leo.kim@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed.billoo@gmail.com \
--cc=tony.cho@atmel.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®