From: kernel test robot <lkp@intel.com>
To: Sanjay R Mehta <sanju.mehta@amd.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Vinod Koul <vkoul@kernel.org>
Subject: [linux-next:master 10616/10945] drivers/dma/ptdma/ptdma.h:31: warning: "PT_OFFSET" redefined
Date: Sat, 28 Aug 2021 01:30:35 +0800 [thread overview]
Message-ID: <202108280128.tQy5HjFe-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3224 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 5e63226c72287bc6c6724d4fc7e157af0e3d7908
commit: 2a99524459ce06d4bc2b82012e53bb3d45a7c15d [10616/10945] dmaengine: ptdma: Initial driver for the AMD PTDMA
config: um-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2a99524459ce06d4bc2b82012e53bb3d45a7c15d
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 2a99524459ce06d4bc2b82012e53bb3d45a7c15d
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=um SHELL=/bin/bash drivers/dma/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/dma/ptdma/ptdma-dev.c:20:
>> drivers/dma/ptdma/ptdma.h:31: warning: "PT_OFFSET" redefined
31 | #define PT_OFFSET 0x0
|
In file included from arch/um/include/asm/thread_info.h:17,
from include/linux/thread_info.h:60,
from include/asm-generic/current.h:5,
from ./arch/um/include/generated/asm/current.h:1,
from include/linux/sched.h:12,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from include/linux/dma-mapping.h:7,
from drivers/dma/ptdma/ptdma-dev.c:13:
arch/x86/um/shared/sysdep/ptrace_user.h:4: note: this is the location of the previous definition
4 | #define PT_OFFSET(r) ((r) * sizeof(long))
|
drivers/dma/ptdma/ptdma-dev.c:52:13: warning: 'pt_log_error' defined but not used [-Wunused-function]
52 | static void pt_log_error(struct pt_device *d, int e)
| ^~~~~~~~~~~~
--
In file included from drivers/dma/ptdma/ptdma-pci.c:24:
>> drivers/dma/ptdma/ptdma.h:31: warning: "PT_OFFSET" redefined
31 | #define PT_OFFSET 0x0
|
In file included from arch/um/include/asm/thread_info.h:17,
from include/linux/thread_info.h:60,
from include/asm-generic/current.h:5,
from ./arch/um/include/generated/asm/current.h:1,
from include/linux/sched.h:12,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from drivers/dma/ptdma/ptdma-pci.c:13:
arch/x86/um/shared/sysdep/ptrace_user.h:4: note: this is the location of the previous definition
4 | #define PT_OFFSET(r) ((r) * sizeof(long))
|
vim +/PT_OFFSET +31 drivers/dma/ptdma/ptdma.h
29
30 #define PT_ENGINE_PASSTHRU 5
> 31 #define PT_OFFSET 0x0
32
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62684 bytes --]
reply other threads:[~2021-08-27 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202108280128.tQy5HjFe-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=sanju.mehta@amd.com \
--cc=vkoul@kernel.org \
/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