From: kernel test robot <lkp@intel.com>
To: Manish Narani <manish.narani@xilinx.com>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>,
Hyun Kwon <hyun.kwon@xilinx.com>,
Piyush Mehta <Piyush.Mehta@xilinx.com>
Subject: [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion
Date: Fri, 17 Dec 2021 06:18:32 +0800 [thread overview]
Message-ID: <20211216221832.GA26062@bd65d657ea95> (raw)
Generated by: scripts/checkincludes.pl
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
phy-zynqmp.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/phy/phy-zynqmp.c b/drivers/phy/phy-zynqmp.c
index 9c12579625460..e23f0d3a4a31c 100644
--- a/drivers/phy/phy-zynqmp.c
+++ b/drivers/phy/phy-zynqmp.c
@@ -13,7 +13,6 @@
*/
#include <linux/clk.h>
-#include <linux/delay.h>
#include <linux/io.h>
#include <linux/kernel.h>
#include <linux/module.h>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion
Date: Fri, 17 Dec 2021 06:18:32 +0800 [thread overview]
Message-ID: <20211216221832.GA26062@bd65d657ea95> (raw)
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
Generated by: scripts/checkincludes.pl
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
phy-zynqmp.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/phy/phy-zynqmp.c b/drivers/phy/phy-zynqmp.c
index 9c12579625460..e23f0d3a4a31c 100644
--- a/drivers/phy/phy-zynqmp.c
+++ b/drivers/phy/phy-zynqmp.c
@@ -13,7 +13,6 @@
*/
#include <linux/clk.h>
-#include <linux/delay.h>
#include <linux/io.h>
#include <linux/kernel.h>
#include <linux/module.h>
next reply other threads:[~2021-12-16 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 22:18 kernel test robot [this message]
2021-12-16 22:18 ` [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-11-12 12:46 [xilinx-xlnx:xlnx_rebase_v5.4 877/1767] drivers/phy/phy-zynqmp.c: linux/delay.h is included more than once kernel test robot
2021-11-12 12:46 ` [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion kernel test robot
2021-11-12 12:46 ` kernel test robot
2021-11-11 20:17 [xilinx-xlnx:xlnx_rebase_v5.4 877/1767] drivers/phy/phy-zynqmp.c: linux/delay.h is included more than once kernel test robot
2021-11-11 20:17 ` [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion kernel test robot
2021-11-11 20:17 ` kernel test robot
2021-10-06 14:38 [xilinx-xlnx:xlnx_rebase_v5.4 877/1767] drivers/phy/phy-zynqmp.c: linux/delay.h is included more than once kernel test robot
2021-10-06 14:38 ` [RFC PATCH xilinx-xlnx] phy: zynqmp: fix duplicated inclusion kernel test robot
2021-10-06 14:38 ` kernel 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=20211216221832.GA26062@bd65d657ea95 \
--to=lkp@intel.com \
--cc=Piyush.Mehta@xilinx.com \
--cc=anurag.kumar.vulisha@xilinx.com \
--cc=hyun.kwon@xilinx.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=manish.narani@xilinx.com \
--cc=monstr@monstr.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.