From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, bart.vanassche@wdc.com,
jthumshirn@suse.de, axboe@kernel.dk, chris@chris-wilson.co.uk,
tvrtko.ursulin@intel.com
Subject: Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings
Date: Mon, 19 Feb 2018 09:42:29 +0530 [thread overview]
Message-ID: <c407c32f-a7b6-06c5-4a03-109445e27427@linux.vnet.ibm.com> (raw)
In-Reply-To: <201802180359.yuetSevh%fengguang.wu@intel.com>
On 02/18/2018 12:58 AM, kbuild test robot wrote:
> Hi Anshuman,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v4.16-rc1 next-20180216]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Anshuman-Khandual/lib-scatterlist-Add-SG_CHAIN-and-SG_END-macros-for-LSB-encodings/20180218-015554
> config: x86_64-randconfig-s3-02180201 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> 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/rts5208/rtsx.h:180:0,
> from drivers/staging/rts5208/rtsx.c:28:
>>> drivers/staging/rts5208/rtsx_chip.h:343:0: warning: "SG_END" redefined
> #define SG_END 0x02
>
> In file included from include/linux/blkdev.h:28:0,
> from drivers/staging/rts5208/rtsx.c:23:
> include/linux/scatterlist.h:69:0: note: this is the location of the previous definition
> #define SG_END 0x02UL
>
>
> vim +/SG_END +343 drivers/staging/rts5208/rtsx_chip.h
SG_END is already defined in a driver. Hence shall we change back
'SG_END' definition as 'SG_EMARK' or any other suggestions ?
next prev parent reply other threads:[~2018-02-19 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 3:33 Anshuman Khandual
2018-02-15 4:28 ` Jens Axboe
2018-02-15 7:36 ` Chris Wilson
2018-02-17 18:33 ` kbuild test robot
2018-02-17 19:28 ` kbuild test robot
2018-02-19 4:12 ` Anshuman Khandual [this message]
2018-02-19 8:08 ` Johannes Thumshirn
2018-02-19 10:10 ` Tvrtko Ursulin
2018-02-19 12:25 ` Andy Shevchenko
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=c407c32f-a7b6-06c5-4a03-109445e27427@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jthumshirn@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tvrtko.ursulin@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®