From: kbuild test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: kbuild-all@01.org, imirkin@alum.mit.edu, efault@gmx.de,
michel@daenzer.net, konrad.wilk@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2
Date: Fri, 5 Jan 2018 01:42:44 +0800 [thread overview]
Message-ID: <201801050110.C0vpY9cy%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180102121358.16215-1-christian.koenig@amd.com>
Hi Christian,
I love your patch! Perhaps something to improve:
[auto build test WARNING on v4.15-rc5]
[also build test WARNING on next-20180104]
[cannot apply to swiotlb/linux-next]
[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/Christian-K-nig/swiotlb-suppress-warning-when-__GFP_NOWARN-is-set-v2/20180104-185406
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-01-04 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 12:13 Christian König
2018-01-02 14:04 ` Mike Galbraith
2018-01-02 15:39 ` Chris Wilson
2018-01-02 16:14 ` Christian König
2018-01-02 20:51 ` Konrad Rzeszutek Wilk
2018-01-03 10:09 ` Christian König
2018-01-04 17:42 ` kbuild test robot [this message]
2018-01-04 17:42 ` [RFC PATCH] swiotlb: _swiotlb_tbl_map_single() can be static kbuild test robot
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=201801050110.C0vpY9cy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=efault@gmx.de \
--cc=imirkin@alum.mit.edu \
--cc=kbuild-all@01.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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®